Accessibility statement

1.What we are aiming for

The goal is that everything on chainpoints.app can be used with a keyboard alone, read aloud by a screen reader, zoomed in without the layout falling apart, and viewed without motion if motion makes you unwell. We treat WCAG 2.1 Level AA as the target we are working toward. We have not had an independent audit against it, so we do not claim to meet it. Where we have actually measured something, we say so below.

2.What is in place today

• –Reduced motion is respected. If your device is set to reduce motion, the animations on the site stop. This is wired into the site stylesheet and into every story page individually.
• –Keyboard focus is visible. Tabbing through the site shows an outline on whatever is selected, so you can always see where you are.
• –Images carry text descriptions. Every image on the main pages has alt text describing what it shows.
• –Colour contrast has been measured, not guessed. On the illustrated story pages several colours were darkened specifically because they measured below the 4.5:1 readability threshold, and the focus outline on those pages was changed for the same reason.
• –Touch targets are sized properly. Buttons and links on the story pages are at least 44 pixels, so they are reachable without precise aim.
• –Pages work without JavaScript. The content on our written pages is in the page itself rather than assembled by scripts afterwards, so it is available to assistive software immediately.

3.Gaps we know about

These are real, and we would rather name them than let you find them:

• –No independent audit yet. Everything above was checked by us. No third party has tested the site, and no assistive-technology user has formally reviewed it.
• –Some pages load inside a frame. The home, About, FAQ and feedback pages render their content in an embedded frame. It works, but it can make screen-reader navigation less direct than it should be.
• –The Chrome extension has not been audited separately. The ChainPoints panel appears on top of Google Flights, and we have not tested that overlay against the same standards as the website.
• –The illustrated stories are the hardest pages. They carry a lot of meaning in layout and colour. The numbers and the point of each one are written out in text, but they are still the pages we would least confidently hand to someone using a screen reader.

4.Telling us something is broken

Email support@chainpoints.app. I read every single email that comes in.

It helps if you can say which page you were on, what you were trying to do, and what you were using at the time, for example a screen reader, keyboard only, or a particular zoom level. If something here is blocking you from doing something, say that plainly and it moves to the front of the queue.

5.Keeping this page honest

This statement is reviewed whenever the site changes in a way that affects any of the points above. When a gap in section 3 is closed it moves up to section 2 rather than quietly disappearing, so the history stays readable. If you want to check something specific, the relevant pages are linked below.