Legal
Accessibility statement
The aim is a site you can use with a keyboard, with a screen reader and at an enlarged zoom. Below is what has actually been checked, and what has not, without varnish.
Last updated: 22 August 2026
What this statement covers
Every page of this site, in every language it is published in. The standard is WCAG 2.2 at level AA, the same one required of public institutions.
What has been checked, and how
Checks are run by measurement across fourteen screen widths and in both themes, after every larger change rather than once before launch. The following has been checked and passes:
- Text contrast against its background of at least 4.5 to 1, in both the dark and the light theme
- Clickable areas of at least 24 pixels, except for word links inside a sentence, where the standard explicitly allows an exception
- Everything can be done from the keyboard, focus is visible, Escape closes what it opened, and focus returns where it came from
- A Skip to main content link as the first element on the page
- The site works without JavaScript: forms submit, term explanations open, navigation works
- Animation stops when you turn on reduced motion in your system
- One first level heading per page, no skipped levels and no duplicated identifiers
- Colour is never the only signal: text or a label always goes with it
- The page language is declared, so a screen reader pronounces it correctly
Level of conformance, and what this statement is not
The site is partially conformant with WCAG 2.2 at level AA. Partially, because this is a self assessment based on automated and manual measurement, not the finding of an independent audit. The site has not been tested with actual screen reader users, and until that is done this statement does not claim full conformance.
What I know is still unresolved
It is only fair to list what measurement finds and what still stands:
- On screens narrower than 320 pixels, three buttons break out of their row
- No testing with screen reader users, only checks of structure and labelling
- No independent accessibility audit
How to report a barrier
If you hit something you cannot use, get in touch by phone, on WhatsApp or through the form on the contact page. It helps to say which page you opened and what you are using, for example a screen reader or the keyboard alone. An answer comes within one working day, and if the fix needs longer I tell you when to expect it.
If you get no answer
If I do not respond within a reasonable time, or the answer does not solve the problem, call again and say it is a barrier you already reported. This statement is voluntary and does not follow from an obligation towards a public body, so the only thing I can promise is a clear deadline and that I keep it.
Report a barrier
Every report is useful to me, both the ones that turn out to be my mistake and the ones that turn out to be the browser's. Get in touch and I answer within one working day.