Accessibility statement
Made to be used by everyone
The aim is that every calculator, estimate and guide here works with a keyboard, a screen reader, a phone, large text and a dark screen, and meets the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
How the pages are built
- Plain HTML first. Choices are real radio buttons, lists, drop-downs and sliders; sections are real headings and lists. ARIA is added only where plain HTML cannot do the job: the search suggestions, the spoken update of a result, and the label on a table that scrolls.
- Every field is labelled in text, and a mistake is explained in words beside the field, not by color alone.
- Keyboard. Everything works without a mouse, focus is always visible, and nothing sticks to the screen and covers what you are reading.
- Size and contrast. Controls are at least 44 pixels tall, text and the edges of fields meet the contrast levels, and the page reflows to a 320-pixel-wide screen and to 200% text without sideways scrolling, apart from wide tables, which scroll inside a labelled box you can reach with the keyboard.
- Motion and color. Animation stops when your device asks for reduced motion, and there is a dark scheme that follows your device.
How it is checked
Before each release a set of automated tests opens every page on a laptop-sized and a phone-sized screen, in light and in dark, and runs the axe accessibility rules for WCAG 2.2 A and AA. Separate tests cover keyboard use, focus rings, target size, zooming, text spacing, reduced motion, heading order and links that share a name but go to different places. The tests are part of the site's code and are run before every release.
Last reviewed: November 5, 2026.
What the checks cannot show
Automated tests find many problems but not all of them. The site has not had an outside accessibility audit, and it has not been tried with every screen reader and browser. Charts are drawings; the figures they show are also written out as text beside them. Some sources we cite, such as government documents, are outside our control.
Reporting a barrier
If something here is hard or impossible to use, write to [email protected] with the page, what you were trying to do and what got in the way. It helps to say which device or assistive technology you use, but it is not required. We read each report and put the fix into the next release.