Our target
This site is built to meet WCAG 2.1 Level AA where practical. Accessibility is treated as part of building each component rather than a review at the end.
What's in place
- Every text and background pair used on the site has been measured against a 4.5:1 minimum, including the smaller secondary and caption text.
- All interactive elements are reachable and operable by keyboard, with a visible focus ring that we never remove.
- A skip link to the main content is the first focusable element on every page.
- Headings run in order without skipped levels, and each page has exactly one
h1. - Form fields have visible labels, errors appear next to the field they belong to and are announced to screen readers, and focus moves to the first invalid field on submit.
- Meaning is never carried by colour alone. Status is always paired with text, an icon, or a shape.
prefers-reduced-motion is respected: transforms are removed and the ambient animations stop entirely.- Buttons, form controls, and navigation items are at least 44 pixels tall. Links inside body text follow the surrounding line height, as is conventional for inline links.
- The layout works down to a 320 pixel viewport without horizontal scrolling.
- App screenshots carry a description of what the screen says, and every fact inside one is also written in the text beside it, so nothing is available only as an image. The dark half of the light and dark comparison is the single exception: it shows the same screen as the light half, so it is hidden from screen readers rather than read out twice.
- The light and dark comparison is a slider. It works with the arrow keys, Home, End, and Page Up and Page Down, and it announces the position as a percentage. With JavaScript unavailable it renders split down the middle, so both themes are still visible and labelled.
What isn't done yet
We'd rather list the gaps than imply there aren't any:
- This site has not yet been audited by an independent accessibility specialist.
- Testing so far has been with keyboard navigation, browser tooling, and contrast measurement. It has not been tested end-to-end with every major screen reader.
- The interactive step-through on the How It Works page is keyboard-operable, but its tab semantics deserve a closer review with assistive technology.
- The mobile app itself is still in development, so no accessibility claim is being made about it yet.
Telling us about a problem
If something here is difficult or impossible to use, we want to know. It's treated as a bug rather than a suggestion. Use the contact form and choose “Report a problem”. Describing the page, what you were trying to do, and the assistive technology you use helps us reproduce it quickly.
