Accessibility statement
The standard aimed at, the real state of it, and how to report a barrier.
What we aim for
WCAG 2.2 at level AA, on every public page and in both languages.
A feature that works in only one language is not finished. The same is true of a feature that works only with a mouse.
What is done
Colour contrast is checked automatically on every build, against the design tokens themselves.
Everything is reachable by keyboard, with a visible focus indicator that is never removed, and a skip link at the top of each page.
Heading structure follows document order, landmarks are named, and both languages are served at separate addresses with the correct language attribute.
What is not
No external audit has been carried out. Validation is the developer's own: heuristics, automated checks and manual testing.
Testing has not yet covered the full range of screen readers and operating systems.
No usability testing has been done with disabled people. That gap is real, and it is stated here rather than left out.
Reporting a barrier
Write to us with the page, what you were trying to do, and the hardware or software you were using.
We acknowledge within five working days and say what we intend to do about it.