Core interaction standard
Keyboard access, visible focus, semantic landmarks, labels, announced errors, contrast, reduced motion, touch targets, 200% zoom, and 360-pixel reflow are release requirements.
Draft for owner review
Accessibility is a build requirement, not an unverified badge.
Core journeys target WCAG 2.2 AA with English LTR and Arabic RTL, but no conformance claim will be made without current test evidence and an accessible feedback route.
Accessibility is a build requirement, not an unverified badge.
Both languages and directions
Arabic and English are tested as first-class experiences, including mixed-script names, numbers, dates, currencies, time zones, directional icons, and expanded text.
Evidence and feedback before claim
Automated checks must be supplemented by keyboard and selected screen-reader review. A named response route and remediation process are required before publication as an effective statement.