Accessibility

Working translation of the canonical Arabic page at /accessibility/. The Arabic version governs on any conflict.

zmam.ai aims to be usable by the widest possible range of users, including people with disabilities. This page describes our current target level, the pages we tested, the methods we used, the known limitations, and how to report a barrier.

Our commitment

We aim to conform to WCAG 2.2 Level AA. This is a self-assessment, not a formal conformance claim. We will update this page as we run automated tools, keyboard-only navigation, and screen- reader testing.

Scope of this review

Homepage: /
Contact: /contact/
Privacy: /privacy/
Responsible use: /responsible-use/
Terms: /terms/

Verification result pages (/v1/verify/...) and any internal token-bearing pages are out of scope — they aren’t indexed and aren’t user-facing in the discovery flow.

Testing methods used

Method	Status
Semantic HTML + heading hierarchy review	Manual, complete
`lang` + `dir` set on the root element	Complete
Text contrast targets 4.5:1 (body) and 3:1 (large)	Manual, complete
Full keyboard navigation via `Tab` + visible focus	Manual, complete
Form labels explicit via `label` and ARIA	Complete
Automated audit with axe / Lighthouse	Not yet performed — scheduled for v0.1
Screen reader testing (NVDA / VoiceOver / TalkBack)	Not yet performed — scheduled for v0.1
Testing with users who have disabilities	Not yet scheduled

What’s in place in this release

Page language set programmatically on the html element: lang="ar" with dir="rtl" for Arabic, and lang="en" with dir="ltr" for English.
Semantic structure: header, nav, main, section, footer elements in a logical heading order.
Interactive form: every field has an explicit label element with matching for/id, and status messages are announced via role="status" and aria-live="polite".
Colour contrast targets the WCAG AA minimums.
Full keyboard navigation with a clearly visible focus ring.
No complex JavaScript components in the UI. The site is largely static and every interaction goes through the form.

Known limitations

No comprehensive automated audit has been performed yet (axe-core, Lighthouse); scheduled for v0.1.
No manual screen-reader testing yet (NVDA, VoiceOver, TalkBack).
The IBM Plex Sans Arabic font is currently CDN-loaded; users on networks that block external fonts will see a fallback.
No user testing with people who have disabilities yet. We will update this list once the first audit runs.

How to report a barrier

If you hit a barrier accessing any part of the site, please let us know so we can address it:

Email: [email protected]
Please include the page URL, the assistive technology you were using (if any), and a description of the difficulty.

We will respond within 10 business days and will update the limitations list above when we discover new barriers.

Version 0.0.1 — Last updated: 2026-05-27