Legal
Accessibility.
What works, what does not yet, and how to tell us we are wrong.
What we build to
WCAG 2.2 at level AA as the target. The site is built from ordinary HTML landmarks and headings rather than from divs pretending to be buttons, which is what makes it navigable by something other than a mouse.
What already works
Every control is reachable by keyboard and shows where the focus is. Text meets contrast requirements in both the light and the dark theme. Animation is switched off for anyone whose system asks for less motion. The Arabic edition is laid out right to left throughout, not a mirrored afterthought, and every page declares its own language so a screen reader pronounces it correctly.
What does not work yet
The PDFs are the weak point. They are laid out for print and their reading order and figure descriptions are not yet properly tagged, so a screen reader will struggle with them even though the site around them is fine. We know, it is not acceptable, and it is being worked on.
Tell us
If something here blocks you, write and say what you were trying to do and what got in the way. Access problems are treated as faults, not as feature requests, and they go to the front of the queue.
Last updated: