Accessibility statement

Accessibility isn't a feature we bolt on — it's the product. adasafe.ai helps organizations find and fix accessibility barriers, so we hold our own site to the standard we help our customers meet.

This statement explains the standard we work toward, how we test, what we know is still imperfect, and how to reach us if something gets in your way.

The standard we work toward

We build and maintain adasafe.ai in alignment with the Kingdom of Saudi Arabia's Digital Government Authority (DGA) accessibility requirements, which are based on the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

This is a statement of the standard we work toward, not a claim of certification. We do not claim DGA certification — no automated tool or self-assessment can certify full conformance, and some success criteria can only be judged by manual and assistive-technology testing, which is ongoing.

How we test

Automated testing

We run our own accessibility scanner — the same axe-core-powered engine we offer customers, evaluating against WCAG 2.1 and 2.2 Levels A and AA — across our marketing, application, and localized pages, and we remediate what it surfaces. Our most recent internal audit covered our public and signed-in pages in every supported language; all issues it found were fixed and re-verified.

Manual and assistive-technology testing

Automated testing cannot catch everything, so we also review the core journeys — running a scan, reading the results, and completing checkout — using a keyboard alone and with screen readers. This manual assistive-technology testing is ongoing and expands as we ship.

Assistive technologies

We test the core journeys with the following assistive technologies:

Known limitations

We are honest about what we haven't finished. Known limitations at the last review:

• Automated tooling cannot evaluate every WCAG success criterion; some can only be confirmed by manual and assistive-technology testing, which is ongoing.
• The payment step is served inside a checkout window provided by our payment processor, Paddle — a third-party surface whose accessibility we monitor but do not directly control.
• Generated PDF reports are tagged for accessibility (PDF/UA-1), but complex data tables within them may still be improved.

Report a barrier

Found a barrier we've missed? Tell us — accessibility feedback goes to the top of our queue. Email us at support@adasafe.ai or use our contact form.

We aim to acknowledge accessibility reports within two business days, and we'll help you reach an accessible alternative while we fix the underlying issue.