Accessibility
Built for everyone, not bolted on after
We target WCAG 2.2 AA, and continuously improve keyboard, screen reader, and reduced-motion experience across the whole site.
Target
We target WCAG 2.2 Level AA conformance across the site. This is a standard we work toward continuously, not a claim of a completed independent audit.
What is implemented today
- A skip-to-content link at the start of every page.
- Visible focus states (focus-visible) on every interactive element.
- Full keyboard navigation, including focus traps and the Escape key in every modal dialog.
- ARIA labels on fields, buttons, and dialogs.
- Required form fields are marked both visually and with aria-required, not by color alone.
- Error messages are tied to their fields via aria-describedby and announced via aria-live.
- prefers-reduced-motion support, plus a manual override inside the Accessibility panel.
- Real RTL for Arabic and real LTR for English, not a visual approximation.
The Accessibility Center
Reachable from the always-visible "Accessibility" button in the header. It offers one-click profiles (Low Vision, Reading Assistance, Reduced Motion, and others) alongside full manual control: text scaling up to 200%, enhanced contrast, wider spacing, and link underlining — without needing to change system-level settings. Choosing a profile never locks out adjusting any individual setting afterward.
Cinematic scenes and text alternatives
Canvas-based scenes respect the simplified-motion mode and pause when scrolled out of view for performance. The essential content of each scene is available as text to screen readers, not locked inside the visual rendering alone.
Ongoing work
Accessibility is ongoing work, not a finished state. We review contrast, touch-target sizing, and keyboard paths regularly as part of every update.
Reporting a barrier
If you encounter a barrier using this site, please let us know through the Contact page on this website — it helps us fix it quickly.