Accessibility

Our Goals and What We Check

We design toward the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We have not completed a full conformance review, so we don't claim full conformance yet. Here is what we do today:

• When a code change is proposed through a pull request, automated checks run axe-core (WCAG 2.0, 2.1 and 2.2 A and AA rules) on 11 key public pages, including the home page, the rankings board, a player profile and a news article, with a phone-width pass on four of them. A serious or critical issue fails the check.
• The same checks run again overnight on any day the site's code changed. They do not yet cover every public page.
• Our colour palette is chosen to meet WCAG contrast minimums (4.5:1 for normal text, 3:1 for large text and interface graphics), and automated tests check the palette's colour pairs.
• Pages have a skip link, landmark regions and a heading structure. Buttons and links are styled with a visible keyboard focus ring.
• The phone menu is tested with a keyboard: focus stays inside it while it is open, Escape closes it, and focus returns to where you were.
• Animations are reduced or turned off when your device asks for reduced motion.
• Buttons and links on phones are sized for touch, generally at least 44 by 44 pixels.

Assistive Technology

Our checks so far are automated and run in Chromium-based browsers. We have not yet tested the site with screen readers such as VoiceOver, NVDA, or TalkBack. If something doesn't work with your browser, screen reader, or other assistive technology, please tell us. Reports from people using assistive technology directly shape what we fix first.

Known Gaps

• Some interactive visualizations, such as the commitments map, don't yet have full keyboard equivalents. The same data is available as a list on the Commitments page, which is linked from the map.
• We have not yet tested with screen readers.
• Our automated checks cover our public pages. Signed-in account pages and the staff tools have had less review.
• Embedded widgets on partner sites, emailed newsletters, and downloadable PDFs have not been reviewed.

Report an Issue

If you run into an accessibility problem anywhere on the site, tell us through the contact form (choose General Inquiry and mention the page and what went wrong). It goes straight to our team's inbox. You can also email us at the address below.