Accessibility

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

zmam aims for the external-scan service to be usable by the widest possible range of users, including people with disabilities. This document describes our current level of conformance, the techniques we apply, known limitations, and how to report an access barrier.

Our commitment

We target WCAG 2.2 Level AA with explicit documentation of known limitations in this release. We treat this commitment as a target conformance, not a formal conformance claim, until the accessibility audit scheduled for v0.1 is complete.

What’s in place in this release

• Direction and language: the site sets lang="ar" (or lang="en") and dir="rtl"/dir="ltr" on the root element, with a visual layout designed for the active reading direction.
• Semantic markup: the site uses semantic HTML5 elements (header, nav, main, section, footer) and headings in a logical hierarchical order.
• Interactive form: form fields have label elements with correct for attributes; status messages are announced via role="status" and aria-live="polite".
• Color contrast: text-on-background contrast targets the minimum 4.5:1 required for body text and 3:1 for large text.
• Keyboard operation: every interactive element is reachable via Tab, with a visible focus indicator.
• No complex JavaScript components: the site is as static as possible (Hugo), with the form as the only interactive component.

Known limitations

• No formal audit has been performed yet with automated tools (axe, Lighthouse) or manual testing with screen readers (NVDA, VoiceOver, TalkBack). This audit will run in v0.1.
• The IBM Plex Sans Arabic font is referenced in the styles but is currently loaded from a CDN; offline or strict-CSP environments may show fallback fonts. A self-hosted variant is in the backlog.
• Verification result pages (/v1/verify/...) are still under development and have not yet undergone independent accessibility testing.
• A full list of limitations will be added here once the formal audit runs.

Reporting an access barrier

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

• Email: [email protected]
• Please include the page, the assistive technology used (if any), and a description of the difficulty.

We will respond within 10 business days, and we’ll update this page with any new limitations we discover.

Later review

• Conformance language: if the founder wishes to use an alternative formulation (e.g., asserting full conformance rather than targeting it), the “Our commitment” section above will be revised.

Version 0.0.1 — Last updated: 2026-05-27