
Accessibility
What works today, what does not yet, and where to report a barrier. Last updated 9 September 2026.
How the site is built
Every control can be reached and used from the keyboard, and the one holding focus is always visibly marked. Buttons showing only an icon carry a text label for screen readers, and each page is built out of real headings and landmarks so a screen reader can skip through it.
Text sits on backgrounds picked for contrast rather than for looks, the layout works from small phones upwards and survives text being enlarged, and everything that moves is decoration: with the system reduce-motion setting on, the animations stop.
Where it falls short
The search box sits in a column that a narrow screen hides, so on a phone there is no way to search. Nobody outside the project has audited the site, so there is no formal conformance claim: it aims at WCAG 2.2 level AA and is not certified against it.
This is an accessibility statement, not a claim that every legal accessibility duty has been met. The operator will review it after independent testing and publish any required national contact or enforcement information before production.
If something blocks you
Write to NicolasUnica@proton.me with the page and what happened. Accessibility problems are treated as bugs, not as feature requests.