Skip to main content
RefundCalculator

Accessibility statement

A site about money that everyone can use is a better site about money. Here is where we are and how to tell us where we fall short.

Target standard

We aim for WCAG 2.2 AA across public pages. Automated checks (axe via Playwright) run in our CI on key journeys; manual keyboard and screen-reader passes are part of the release process for calculator pages.

What that means in practice

  • Semantic HTML with labelled landmarks, a skip-to-content link, and visible focus states.
  • Every calculator page reads fully without JavaScript — the explanation is in the HTML; only the form hydrates.
  • Form inputs have programmatic labels, errors are announced via role="alert", and results use aria-live regions.
  • Colour is never the only carrier of meaning; contrast meets AA for text.
  • Motion respects prefers-reduced-motion.
  • One self-hosted font family at readable sizes; text can be resized to 200%.

Known limitations

  • Some older GOV.UK pages we link out to have their own accessibility quirks — outside our control.
  • The cookie manager traps keyboard focus only while open; closing it returns focus to the page normally.

Report a problem

Accessibility reports go to the front of the queue. Use the contact form and tell us the page, what went wrong, and the technology you use — we aim to respond within five working days and to fix genuine barriers in the next release.