Accessibility statement

Our standard

We aim to meet WCAG 2.2 at level AA across the whole site, one version newer than the WCAG 2.1 AA we check other sites against.

How we test

Before any change goes live, every kind of page on the site is checked automatically, and a change that fails doesn’t ship:

• automated accessibility checks against WCAG 2.2 A and AA, at phone and desktop sizes, with the phone menu open as well as closed;
• that nothing scrolls sideways on a screen 320 pixels wide;
• text size, tap targets, and form fields that would make a phone zoom in.

What we build in

• Plain HTML: real links, buttons, headings and labels, and a visible outline wherever the keyboard is.
• Color is never the only sign of anything: every score and band is also given in words.
• The live scan tells screen readers its milestones, not every change, and motion stops when your device asks for reduced motion.
• On the maps, every place is a named link you can reach with the keyboard, a link lets you skip past them, and the list below each map holds every place too.
• The site is set in Atkinson Hyperlegible, a typeface the Braille Institute designed to be easy to read for people with low vision.

Where we fall short

• The smallest places on the maps are small targets. Every place on a map is also in the list below it, at full size.
• Reports show screenshots of other websites as evidence of a problem. Each is described in words beside it, and the screenshot itself shows another site’s content as it is, problems included.
• Our testing is automated; we haven’t yet had the site reviewed by people who use assistive technology every day. We plan to.

Tell us about a barrier

If anything on the site stops you, or you need a page or a report in another format, tell us through our contact form. A person reads every message, and we aim to reply within five business days.

About this statement

Last updated November 2, 2026. We review it whenever the site changes in a way that affects it.