Accessibility statement for the MoneyHelper legacy tools

This accessibility statement applies to interactive tools on the website at: https://www.moneyhelper.org.uk/.

This website is run by the Money and Pensions Service. We want as many people as possible to be able to use this website. For example, that means you should be able to:

• change colours, contrast levels and fonts
• zoom in up to 300% without the text spilling off the screen
• navigate most of the website using just a keyboard
• navigate most of the website using speech recognition software
• listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
• access the site on smaller devices.

We’ve also made the website text as simple as possible to understand. 

We know some parts of this website are not fully accessible:

• Some select menus don’t have a permanently visible name.
• Some focus indicators have insufficient colour contrast.
• The expanded and collapsed state of some help buttons isn’t conveyed to screen readers.
• Some groups of form fields are displayed as a group but aren’t labelled properly in the HTML.
• Some form fields which require input don’t have labels or instructions.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2Opens in a new window  AA standard, due to the non-compliances listed below.  

The content listed below is non-accessible for the following reasons.

• Next / Previous buttons are missing labels.
  • Description: Screen reader users may not understand the purpose of the buttons if the label is missing.
  • WCAG Criterion: 1.1.1 Non-text content (A).
• The input label should specify the answer needs to be in pounds / percentages / years.
  • Description: Prefix’s and years suffix’s are not communicated other than visually so needs to be included within the label to indicate the answer is in pounds / percentages / years.
  • WCAG Criterion: 2.4.6 Headings and Labels (AA).
• Keyboard focus is partially obscured by the next button.
  • Description: People using a keyboard may be unable to identify which elements are currently in focus.
  • WCAG Criterion: 2.4.11 Focus not obscured (AA).
• Tab panels implementation.
  • The tabs at the top of the are (correctly) conveyed as “Tabs”. However, the expected keyboard behaviour is to arrow between the options, which is not enabled. The aria-controls ‘tabpanels’ are missing, each section of content associated with a tab should be marked up as a tab-panel.
  • WCAG Criterion: 4.1.2 Name, Role, Value (A).
• Summary so far and your progress not automatically announced.
  • As a user inputs in each text field, the text summary / progress total updates. The updated text is not announced to screen reader users.
  • WCAG Criterion: 4.1.3 Status Messages (AA).

• The Go to next event button focus indicator has insufficient colour contrast against the background.
  • Description: When the focus indicator has insufficient colour contrast, it can be difficult or impossible for sighted keyboard users to determine which control currently has focus. Current contrast ratio: Focus outline colour: #B9DD48, Background: #FFFFFF, Contrast ratio: 1.6:1.
  • WCAG Criterion: 1.4.11 Non-text Contrast (AA).
• The HTML select menus are missing a permanently visible label.
  • Description: When a selection is made the visible label text changes. This is problematic for people with cognitive impairments that affect short-term memory, as well as a more general usability issue.
  • WCAG Criterion: 3.3.2 Labels or Instructions (A).
• The reading order of the page isn't logical.
  • Description: The design of the Timeline uses CSS absolute positioning to achieve the layout. However, the order in which the content appears in the HTML doesn’t follow the visual layout. When a specific reading order is important, but is only achieved visually, it won't be conveyed to people using screen readers who may find the content doesn't make sense.
  • WCAG Criterion: 1.3.2 Meaningful Sequence (A).
• The Timeline can only be operated using a dragging movement.
  • Description: People with mobility or motor disabilities may have difficulty performing dragging movements. Similarly, those with a mounted device or who use assistive technology, such as eye trackers, may not be able to perform these actions.
  • WCAG Criterion: 2.5.7 Dragging Movements (AA).
• The Carousel and Timeline page regions aren't marked up in the HTML.
  • Description: Information about the structure of the content, which is conveyed visually, but not in the HTML code will not be available to people using screen readers. This makes it harder for them to navigate and understand the content.
  • WCAG Criterion: 1.3.1 Info and Relationships (A).

• HTML Table is not required.
  • The HTML table is not required for the breakdown chart.
  • WCAG Criterion: 1.3.1 Info and relationships (A).
• The input label should specify the answer needs to be in pounds / percentages / years.
  • Prefix’s and years suffix’s are not communicated other than visually so needs to be included within the label to indicate the answer is in pounds / percentages / years.
  • WCAG Criterion: 2.4.6 Headings and Labels (AA).
• Tabs panel implementation.
  • The expected keyboard behaviour is to arrow between the options, and the tab key is then used to move focus into the content. Currently the focus is automatically moved into the first form element when a user selects a tab panel. Allow users to manually enter into the tab content.
  • WCAG Criterion: 3.2.2 On Input (A).
• Summary so far and your progress not automatically announced.
  • WCAG Criterion: 4.1.3 Status Messages.

• The tab interface is missing the appropriate role, property and state information.
  • Description: When the role of a control doesn't match its actual purpose or is missing, people who use a screen reader may not know how to interact with it, understand its current state, or may not be given appropriate feedback when the state is changed.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• Labels or instructions aren’t provided when form fields require input.
  • Description: When form controls lack instructions, all users are likely to have some degree of difficulty in understanding what information is required. This can be particularly problematic for people with cognitive or learning disabilities.
  • WCAG Criterion: 3.3.2 Labels or Instructions (A).
• The expanded and collapsed state of the show help button isn’t conveyed to screen readers.
  • Description: People who use a screen reader won’t understand the function of the button or its present state.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• The custom focus indicators have insufficient colour contrast against the background.
  • Description: When the focus indicator has insufficient colour contrast, it can be difficult or impossible for sighted keyboard users to determine which control currently has focus. Current contrast ratio:
    • focus outline colour: #DAAF2D
    • background: #FFFFFF
    • contrast ratio: 2.2:1
    • WCAG Criterion: 1.4.11 Non-text Contrast (AA).

• Radio buttons are not grouped in a fieldset / legend.
  • 1.3.1 Info and Relationships (A).
• Error messages aren’t associated with the inputs.
  • Error messages are not automatically announced when the relevant input receives screen reader focus.
  • 1.3.1 Info and Relationships (A).
• The input label should specify the answer needs to be in pounds / percentages / years.
  • Prefixes and suffixes like "years" are not communicated other than visually, so they need to be included in the label to indicate the answer format.
  • 2.4.6 Headings and Labels (AA).
• Budget summary not automatically announced.
  • As a user inputs values in each text field, the text summary updates. The updated text is not announced to screen reader users.
  • 4.1.3 Status Messages (AA).

• The current item in the progress is indicated by a change in colour to the text and underline but, not in the HTML.
  • Description: If a form has a known number of steps, a step-by-step indicator can help people using screen readers to orient themselves. Although the same information is provided in the page heading, this information isn’t always available when browsing out of context.
  • WCAG Criterion: 1.3.1 Info and Relationships (A).
• When the form error notification appears dynamically, without automatically receiving keyboard focus, it's not announced by screen readers.
  • Description: People using a screen reader may not be aware of the notification or the error status of the content.
  • WCAG Criterion: 4.1.3 Status Messages (AA).
• The HTML select menus are missing a permanently visible label.
  • Description: When a selection is made the visible label text changes. This is problematic for people with cognitive impairments that affect short-term memory, as well as a more general usability issue.
  • WCAG Criterion: 3.3.2 Labels or Instructions (A).
• The HTML select menus don't have an accessible name.
  • Description: When a control lacks a name, it will be announced by assistive technologies as a generic control. This won’t be sufficient to convey the control's purpose and may make it difficult or impossible for people who use screen readers to make sense of the control or to confidently use it.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• Form errors are overly verbose.
  • Description: Form inputs use the aria-describedby attribute to relate the relevant error notifications. However, the ID value for the error notification is repeated to form a concatenated message which repeats the notification multiple times (as many as six times).
  • WCAG Criterion: Best Practice.

• The HTML select menus don't have an accessible name.
  • Description: When a control lacks a name, it will be announced by assistive technologies as a generic control. This won’t be sufficient to convey the control's purpose and may make it difficult or impossible for people who use screen readers to make sense of the control or to confidently use it.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• The HTML select menus are missing a permanently visible label.
  • Description: When a selection is made the visible label text changes. This is problematic for people with cognitive impairments that affect short-term memory, as well as a more general usability issue.
  • WCAG Criterion: 3.3.2 Labels or Instructions (A).
• The current item in the progress is indicated by a change in colour to the text and underline but, not in the HTML.
  • Description: If a form has a known number of steps, a step-by-step indicator can help people using screen readers to orient themselves. Although the same information is provided in the page heading, this information isn’t always available when browsing out of context.
  • WCAG Criterion: 1.3.1 Info and Relationships (A).
• Labels or instructions aren’t provided when form fields require input.
  • Description: When form controls lack instructions, all users are likely to have some degree of difficulty in understanding what information is required. This can be particularly problematic for people with cognitive or learning disabilities.
  • WCAG Criterion: 3.3.2 Labels or Instructions (A).
• When in the error state and focused the custom focus indicators use a change in colour alone to indicate the focus state.
  • Description: Because the red outline overrides the default focus state (which is highly visible) people with low vision or colour blindness may not realize that the menus are focused.
  • WCAG Criterion: 1.4.1 Use of Colour (A).
• After the form is submitted and errors are detected the error text doesn't provide enough context or information for correcting the errors.
  • Description: The visible error notifications contain a generic “Please confirm” message which doesn’t indicate which input is in error (when there are multiple grouped inputs) and the visual indicator (arrow pointing down) only indicates one of the inputs. In some instances, the previously entered information is cleared and must be entered again when the form is returned after validation, compounding the issue further. While people may understand that an input error has occurred, they may not be able to understand how to appropriately correct the error or which input to correct.
  • WCAG Criterion: 3.3.3 Error Suggestion (AA).
• After form validation information previously entered is lost.
  • Description: After form validation, the previously entered information is cleared and must be entered again when the form is returned. Reducing the need to recall information provided in a previous step helps all users. People with cognitive or learning disabilities, however, may find it especially difficult to complete a process if they are required to remember, re-type, or repeat information.
  • WCAG Criterion: 3.3.7 Redundant Entry (A).
• The accessible name of the form text fields doesn't match the visible label.
  • Description: All the form fields contain the same aria-labeled by value which points to the first text field. This overrides the visible label resulting in all the form fields having the same name. People who use speech input won't be able to interact with the control using the visible text. People using screen readers may find it confusing when the label text doesn't match the accessible name or understand the form when browsing out of context.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• The Value table heading doesn’t sufficiently describe the topic or purpose of the corresponding column.
  • Description: The Value table heading contains a text string which appears to be a defect. When the table heading doesn’t adequately convey the purpose of the column, people who use screen readers may find it difficult to understand or make sense of it.
  • WCAG Criterion: 2.4.6 Headings and Labels (AA).

• The expanded and collapsed state of the Further information button isn’t conveyed to screen readers.
  • Description: People who use a screen reader won’t understand the function of the button or its present state.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• Text inputs use placeholders as a label.
  • Description: After information is entered into the field, the visible hint or instructions for the required information is removed. This is problematic for people with cognitive impairments that affect short-term memory, as well as a more general usability issue as placeholder text with sufficient color contrast may be interpreted as input. Additionally, the default colour contrast of placeholder text is poor in many browsers, making it difficult for people with low vision to perceive it.
  • WCAG Criterion: 3.3.2 Labels or Instructions (A).
• The HTML select menus don't have an accessible name.
  • Description: The select menu labels have been hidden using the CSS display:none; property which hides it from everyone. When a control lacks a name, it will be announced by assistive technologies as a generic control. This won’t be sufficient to convey the control's purpose and may make it difficult or impossible for people who use screen readers to make sense of the control or to confidently use it.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• The Setting up a workplace pension scheme HTML select menus don't have an accessible name.
  • Description: The label for attribute contains an invalid ID value. When a control lacks a name, it will be announced by assistive technologies as a generic control. This won’t be sufficient to convey the control's purpose and may make it difficult or impossible for people who use screen readers to make sense of the control or to confidently use it.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• The custom focus indicators have insufficient colour contrast against the background.
  • Description: When the focus indicator has insufficient colour contrast, it can be difficult or impossible for sighted keyboard users to determine which control currently has focus. Current contrast ratio: Focus outline colour: #DAAF2D, Background: #FFFFFF, Contrast ratio: 2.2:1.
  • WCAG Criterion: 1.4.11 Non-text Contrast (AA).
• The SVG icons contain text descriptions which duplicate the surrounding content.
  • Description: Decorative images are those which aren't relevant to the meaning or purpose of the content. If decorative images have text descriptions it can add to the amount of information a person who uses a screen reader has to process.
  • WCAG Criterion: 1.1.1 Non-text Content (AA).
• The tab interface is missing the appropriate role, property and state information.
  • Description: When the role of a control doesn't match its actual purpose or is missing, people who use a screen reader may not know how to interact with it, understand its current state, or may not be given appropriate feedback when the state is changed.

• The custom focus indicators have insufficient colour contrast against the background.
  • Description: When the focus indicator has insufficient colour contrast, it can be difficult or impossible for sighted keyboard users to determine which control currently has focus. Current contrast ratio: Focus outline colour: #DAAF2D Background: #FFFFFF Contrast ratio: 2.2:1.
  • WCAG Criterion: 1.4.11 Non-text Contrast (AA).
• Icons do not have appropriate alternative text.
  • Description: Images that convey information should have alternative text descriptions to ensure people using screen readers can also access the same information. If the image is decorative and provides no additional context or content then it should be identified as such.
  • WCAG Criterion: 1.1.1 Non-text Content (AA).
• The SVG icons contain text descriptions which duplicate the surrounding content.
  • Description: Decorative images are those which aren't relevant to the meaning or purpose of the content. If decorative images have text descriptions it can add to the amount of information a person who uses a screen reader has to process.
  • WCAG Criterion: 1.1.1 Non-text Content (AA).
• The expanded and collapsed state of the Further information button isn’t conveyed to screen readers.
  • Description: People who use a screen reader won’t understand the function of the button or, its present state.
  • WCAG Criterion: 4.1.2 Name Role Value (A).
• Controls are not accessible on keyboard.
  • Description: People who use a keyboard (including people who use a screen reader) will be unable to use these controls.
  • WCAG Criterion: 2.1.1 Keyboard (A).

• Radio buttons are not grouped in a fieldset / legend.
  • 1.3.1 Info and Relationships (A).
• Error messages aren’t associated with the inputs.
  • 1.3.1 Info and Relationships (A).
• The input label should specify the answer needs to be in pounds / percentages / years.
  • 2.4.6 Headings and Labels (AA).
• There is no announcement when a filter is removed or when the results is sorted.
  • The filter has a number of interactive components, a keyboard user navigating through the page may find this as a tedious task, especially once a user submits a filter, they will have to tab through the filters before reaching the results.
  • 4.1.3 Status Messages (AA).
• Dynamic notifications are not announced automatically to screen reader users.
  • 4.1.3 Status Messages (AA).

This website contains embedded tools that are hosted on a legacy platform. All of the accessibility issues listed here concern those tools. We are currently in the process of replacing these tools with new versions built on our new platform. We will commission third-party accessibility audits of these tools, and will conduct usability testing with participants with disabilities.

We will revise this accessibility statement to reflect improvements made and any new issues no later than 30 September 2025.

This statement was last updated on 10 January 2025.

This website was last tested on 22 February 2024. The test was carried out by Nomensa Ltd.

The testing used a combination of accessibility evaluation tools, visual inspection of code and testing with assistive technology to evaluate a representative subset of 61 test samples across 10 tools.

The testing assessed the following pages:

• Baby costs calculator: https://www.moneyhelper.org.uk/en/family-and-care/becoming-a-parent/use-our-baby-costs-calculator
• Baby money timeline: https://www.moneyhelper.org.uk/en/family-and-care/becoming-a-parent/use-our-baby-money-timeline
• Budget planner (old version): https://www.moneyhelper.org.uk/en/everyday-money/budgeting/use-our-budget-planner
• Mortgage affordability calculator: https://www.moneyhelper.org.uk/en/homes/buying-a-home/use-our-mortgage-affordability-calculator
• Pension calculator: https://www.moneyhelper.org.uk/en/pensions-and-retirement/pensions-basics/use-our-pension-calculator
• Redundancy pay calculator: https://www.moneyhelper.org.uk/en/work/losing-your-job/use-our-redundancy-pay-calculator
• Retirement adviser directory: https://www.moneyhelper.org.uk/en/pensions-and-retirement/taking-your-pension/use-our-tool-to-find-a-retirement-adviser
• Travel insurance directory: https://www.moneyhelper.org.uk/en/everyday-money/insurance/use-our-travel-insurance-directory
• Workplace pension contribution calculator: https://www.moneyhelper.org.uk/en/pensions-and-retirement/auto-enrolment/use-our-workplace-pension-calculator.