Accessibility statement

This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA on every page and in every calculator. The assessment is not complete, so we do not yet claim that it does.

Status: assessment not complete

An AI assistant has run automated and scripted checks, and the site's owner has tested it with VoiceOver, with a keyboard alone and with zoom. The tests not yet done are listed under What has not been tested. Automated checks alone cannot show that a site meets the guidelines. We will not describe the site as meeting WCAG 2.2 AA until every check below is done and every failure is fixed.

What this statement covers

Every page of this site and the four calculators, in their normal state, with an error showing, with details opened and after a result has changed.

What you should be able to do

What has been tested

Unless a test says otherwise, it used Chrome 156, Firefox 158 and WebKit 27.2, the engine Safari is built on, on macOS (Apple silicon), driven by script. The tests ran on 22 October 2026.

Automated rules
axe-core 4.11 ran on every page, at phone and desktop widths, in light and dark schemes, and with each calculator showing a result and an error. It found no violations. Where it could not judge the contrast of some text, a script measured each case, and none was below the required ratio.
Reflow
At 320 CSS pixels wide, no page scrolls sideways. Wide tables and charts scroll inside their own area.
Text spacing
With the spacing of WCAG 1.4.12 applied, no text was cut off on any page.
Target size
No control is smaller than 24 by 24 CSS pixels, apart from links inside a sentence, which the guidelines exempt. Some controls are between 24 and 43 pixels high, below our own aim of 44.
Keyboard order and visible focus
A script pressed Tab through every page, or Option-Tab in WebKit, which reaches links as Tab does in Safari with its setting to highlight each item on. Every control was reached, in reading order, with an outline style set when focused, and none was covered by other content.
Headings
No page skips a heading level.
Without JavaScript
Every explanation can be read. With JavaScript off, each calculator shows a notice instead of its form, and none of the sentences that tell a reader what to enter or copy. The triple lock calculator, the rule comparison and the history explorer also show a default result; the budget explorer's notice points to its example budgets, set out in full on its page. Each calculator was also loaded with its own script blocked, when the notice adds that the script did not run and how to report it, and with its script held back, when neither the form nor the notice shows until it runs.
VoiceOver with Safari on a Mac
A person listened to every page from top to foot, with every disclosure open, and listed each page's headings, tables, links and landmarks; worked through the four calculators, hearing entered figures, errors, results, charts and their tables, and a copied link; and moved through every table by row and by column. What was found was fixed and heard again. Safari with VoiceOver on macOS, used by a person. Tested on 22 October 2026.
VoiceOver with Safari on an iPhone
A person worked through the triple lock calculator. What was found was fixed and checked again, apart from the two points listed under what has not been tested. Safari with VoiceOver on iOS, used by a person. Tested on 17 October 2026.
Keyboard use by a person
A person tested the site with a keyboard alone, in Chrome and then in Firefox. Two faults were found and fixed: the "Back to top" link could not be reached with Tab, and the history explorer's copy button gave no visible sign that it had worked. Chrome and Firefox on macOS, used by a person. Tested on 18 October 2026.
Zoom to 200% and 400%
A person zoomed every page to 200% and 400% in Chrome, and the costs page and the budget explorer to 400% in Firefox. One fault was found and fixed: on the costs page, the outline of a focused table covered the first letter of its caption. Chrome and Firefox on macOS, used by a person. Tested on 18 October 2026.

What has not been tested

VoiceOver on an iPhone for the other three calculators
On an iPhone the budget explorer, the rule comparison and the history explorer have not been tested. On the triple lock calculator on an iPhone, one paragraph was read twice on one pass, which could not be repeated, and VoiceOver read the summary "At a glance" after each digit typed. Both are still to be looked at.
NVDA with a Windows browser
NVDA is a free screen reader for Windows. Not yet tested. No Windows computer was available.
Touch on a phone without a screen reader
Tested at phone width on a computer, and on an iPhone only with VoiceOver, as above.
The automated and scripted checks in Safari itself
They ran in WebKit, the engine Safari is built on, because Safari would not accept a test script on our computer. Safari itself was used with VoiceOver, as above.
Use by disabled and older readers
We have held no usability sessions.
Independent audit
No one has carried one out.
The "Out of date" note in the calculators
Added on 5 October 2026. When a figure is half typed, the last result stays with this note. It was looked at in screenshots. On the rule comparison, VoiceOver with Safari on a Mac said the field, what to enter and that the result shown is out of date on leaving a wrong figure. The note has not been heard in the other calculators, and the automated rules did not scan that state.
Changes to a form when a choice is made
Some choices change other fields at once: the household, the budget period, the scenario, the number of years, the first year and the pension series. With VoiceOver, choosing a household said nothing of the field it adds or empties; it now says so. A person has not yet judged whether each change is clear.

Known problems

No failure found in testing is still open. That covers only the tests listed above.

Report a problem

If you cannot use part of this site, tell us what you were trying to do and what happened.

The link opens this site's issues on GitHub, the website that holds its source files. Choose New issue to send a report. It is the only way to report a problem: there is no email address. You need a GitHub account to send a report. It is free, but it is still a barrier, and it is a known limit of this site.

Preparation of this statement

The assessment is recorded as of 22 October 2026. The tests above give the dates they ran. The full assessment, criterion by criterion, is kept with the site's source files.

Content of this page last changed on 18 October 2026.

Back to top