Accessibility
What works today, and what we know does not.
Last updated
Where we stand
We build with accessibility in mind and we have not had the site audited. So this page tells you what was deliberately done and what is still unverified, rather than claiming a conformance level nobody has measured. We would rather be useful than reassuring.
What was built in on purpose
- Every page works from the keyboard alone, and the focus outline is always visible — never removed to tidy up the design.
- Body text and muted text were both checked against their backgrounds for contrast. The lighter grey we started with failed, so it is not used for text.
- Form fields have real labels, and an error is tied to its field so a screen reader announces it rather than leaving it stranded on the page.
- Photos carry a description from the caption where there is one.
- Light and dark both follow your system setting.
- Animation is reduced automatically if you have asked your system for that.
- Decorative emoji are hidden from screen readers, so nobody has to listen to a paw print.
- The first tab on any page is a skip link straight to the content.
- Headings run in order — no page jumps a level, so navigating by heading reaches everything.
- Links in navigation and footers are at least 24px tall, which is what WCAG 2.2 asks for.
What we know is not right yet
- No audit has been done, by us or anyone else, against WCAG or any other standard.
- It has not been tested with real screen readers, only built to the rules.
- Photos posted without a caption fall back to a generic description, because we have no way to know what is in the picture.
- Zoom and small-screen behaviour have had a light check rather than a thorough one.
If something blocks you
Please tell us — this is the fastest way for it to get fixed, and a specific report beats a general one. What page, what you were trying to do, and what happened instead: [email protected].
If something on this site stops you doing what you came to do, we treat it as a bug, not a request.