Accessibility statement

What we are aiming at

WCAG 2.2 level AA as a floor, not a target. This site is a campaign about people being left out of a structure; it would be a poor look to leave people out of the site.

What has been done

Every page works without JavaScript. Not "degrades" — works. The navigation is plain links, every chart is a real HTML table in the markup, the support button is a real form with a real action, and the step explorer is a readable document.
Every page works without CSS, in a sensible reading order.
Full keyboard operation, including the mega menu (arrow keys between sections, Escape to close, Tab out to close), the mobile overlay (focus trapped, focus restored on close), the charts (one tab stop, arrow keys between data points) and the flow diagram.
Visible focus everywhere. A two-part ring — a solid core plus an amber halo — so it stays visible on paper, on green, on amber and over photography.
Contrast checked automatically on every page, in light and dark mode, against the real composited background rather than the declared one. Body text clears 4.5:1 and large text 3:1.
No information carried by colour alone. Chart series carry a pattern as well as a colour; confidence markers carry a word and a glyph as well as a colour.
Reduced motion is honoured: every animation duration collapses to zero, the hero stops moving, the counter jumps to its final value and the flow diagram switches seasons instantly.
Dark mode across every component and chart.
No horizontal scrolling at 320px on any page. Wide content scrolls inside its own container.
Live regions announce filter results, chart navigation and form validation without moving focus.

How it was tested

Automated checks run on every page at 320px, 768px and 1440px in both light and dark mode: contrast against the composited background, horizontal overflow, heading order, landmark labelling, accessible names for every focusable control, and images without dimensions or alternative text. Keyboard paths were driven with real key events rather than assumed.

What we know is not right yet

Being honest about this is the point of a statement like this one.

No screen-reader testing with a real user. The markup has been built carefully and checked programmatically, but nobody who uses a screen reader daily has yet been through this site. That is the biggest gap and we would like to fix it.
The schematic map is decorative-plus. It is hidden from assistive technology on purpose, because the club list beside it carries the same information in a better form. If you find the list harder to use than the map, tell us — that would mean we got the balance wrong.
The funding flow diagram is complex. Every node and ribbon has a descriptive label and there is a full table underneath, but a Sankey is an inherently visual thing and the table may simply be the better route for some readers. It is one click away and always present in the page.
Long words at 320px. A few club and league names are long enough to sit tightly in narrow columns. No overflow, but not elegant.
The display typeface is a system stack. Which face you get depends on your operating system, so the exact look varies more than it would with a self-hosted font.

If something blocks you

Please tell us. A specific description — the page, what you were trying to do, what happened, and what you were using — is enormously more useful than a general report, but send it either way.

Report a barrier

We aim to reply within five working days and to fix genuine blockers before anything else in the queue, including new features.

Enforcement

This is a voluntary campaign site rather than a public sector body, so the Public Sector Bodies Accessibility Regulations do not apply to it. We are holding ourselves to the standard anyway. If you are not satisfied with our response you can contact the Equality and Human Rights Commission.