Accessibility

What we aim for

We are working towards WCAG 2.1 Level AA. We are not claiming to have reached it — the list below is deliberately honest about both sides.

What is in place

• Readable text. Body text is never smaller than 16px, and every colour pairing we use for text meets the AA contrast threshold. Our brand orange fails it at small sizes, so it is used only for large headings.
• Keyboard navigation. Everything can be operated without a mouse. Focus is always visible as a purple outline, and a “Skip to content” link appears on the first Tab of any page.
• Dialogs behave. The report dialog and the mobile menu keep keyboard focus inside them, close on Escape, and return focus to whatever opened them.
• Labelled forms. Every field has a real label, errors are linked to the field they belong to and announced, and no error depends on colour alone.
• Sensible structure. Proper headings and landmarks, so a screen reader can jump around instead of reading everything.
• Reduced motion. If your system asks for less motion, animations are switched off.
• Built for phones first. Everything works on a small screen and reflows when text is enlarged.

What is not done yet

• We have not tested with real screen reader users. Automated checks catch a fraction of what matters; this is the gap we most want to close.
• No formal WCAG audit has been carried out.
• The site is in English only. Given who it is for, other languages matter and are planned.

Tell us when we get it wrong

If something here is hard to use, that is a fault in the site, not in you. Please tell us through the contact page — what you were trying to do, and what got in the way. We will fix it and tell you when we have.