Accessibility statement for Pension Annual Allowance Calculator service

This accessibility statement explains how accessible this service is, what to do if you have difficulty using it, and how to report accessibility problems with the service.

This service is part of the wider GOV.UK website. There is a separate accessibility statement for the main GOV.UK website .

This page only contains information about the Pension Annual Allowance Calculator service, available at https://www.tax.service.gov.uk/pension-annual-allowance-calculator.

Using this service

This service enables users to use a calculator to check if their pension savings are more than their annual allowance, or if they have any unused annual allowance to carry forward.

This service is run by HM Revenue and Customs (HMRC). We want as many people as possible to be able to use this service. This means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • get from the start of the service to the end using just a keyboard
  • get from the start of the service to the end using speech recognition software
  • listen to the service using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We have also made the text in the service as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this service is

This service is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

Some people may find parts of this service difficult to use:

  • Page titles don’t include the service name. This does not follow HMRC's design pattern and does not make it clear what service you are on when using a screen reader. We will be updating these so they follow our pattern.
  • Some of the information is read out twice by a screen reader because the designs do not follow the pattern. We will fix this so that all of the information is only read once.
  • On one of the pages, there is a link to guidance which opens in the same tab, meaning users lose their progress. We will change this so it opens in a new tab and users can carry on with the journey.
  • On all pages, error messages are not linked to the fields they relate to. This means they will not be read by assistive technology if the user moves straight to the field. We will fix this so they are all linked to the field and read out properly. Users can still use the browse mode to find this information.

What to do if you have difficulty using this service

You can contact HMRC for extra support if you need help with filling in forms or getting a different format, like large print, audio recording or Braille.

Reporting accessibility problems with this service

We are always looking to improve the accessibility of this service. If you find any problems that are not listed on this page or think we are not meeting accessibility requirements, report the accessibility problem (opens in a new tab).

If you are not happy with our response

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the 'accessibility regulations'). If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS) or the Equality Commission for Northern Ireland (ECNI) if you live in Northern Ireland.

Contacting us by phone or getting a visit from us in person

We provide a text relay service if you are deaf, hearing impaired or have a speech impediment.

We can provide a British Sign Language (BSL) interpreter, or you can arrange a visit from an HMRC advisor to help you complete the service.

Find out how to get extra support from HMRC .

Technical information about this service’s accessibility

HMRC is committed to making this service accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This service is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non‐accessible content

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

Non‐compliance with the accessibility regulations

There is extra information being read out that users should not hear when using a screen reader. This fails WCAG 2.1 - Understanding Success Criterion 2.4.1 - Bypass Blocks and Understanding Success Criterion 4.1.1 - Parsing. We will fix this to remove anything that a user doesn’t need to hear. We plan to fix this compliance issue by 31 July 2021.

When there is an error on the page, we usually put the word ‘Error’ into the page title. We have not done this in the service. This fails WCAG 2.1 - Understanding Success Criterion 3.3.1 - Error Identification. We will be updating our page titles to contain the word ‘Error’ when there is an error on the page. We plan to fix this compliance issue by 31 July 2021.

When there is an error, the keyboard focus is on the wrong part of the page. This makes it more difficult to work out if there has been an error. This fails WCAG 2.1 - Understanding Success Criterion 3.3.1 - Error Identification. We will fix this so the error state has keyboard focus and the user knows there has been an error. We plan to fix this compliance issue by 31 July 2021.

We ask for money amounts within this service, and have not added pound signs to show that this is the currency we want users to use. This fails WCAG 2.1 - Understanding Success Criterion 3.3.2 - Labels or Instructions. We will fix this to add in pound signs so the user knows we want amounts in great british pounds. We plan to fix this compliance issue by 31 July 2021.

There are some links in the footer of the service that are not read out by a screen reader. This fails WCAG 2.1 - Understanding Success Criterion 1.3.1 - Info and Relationships. We will fix this so that all items in the footer are read out by a screen reader. We plan to fix this compliance issue by 31 July 2021.

We have a time limit in the service before we reset all your answers for your security. We do not have a message that tells users we will do this. This fails WCAG 2.1 - F58 - Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out and Understanding Success Criterion 2.2.6 - Timeouts. We will add a message telling users when they are going to be timed out and give the option to stay in the service. We plan to fix this compliance issue by 31 July 2021.

We have hint text to help users give the right information. This has been coded wrong so it will not be read out by a screen reader or screen magnifier. This fails WCAG 2.1 - Understanding Success Criterion 4.1.1 - Parsing. We will fix this so a screen reader can read out all hint text. We plan to fix this compliance issue by 31 July 2021.

Some of the pages in our service have checkboxes that do not have focus when using high contrast mode. This fails WCAG 2.1 - Understanding Success Criterion 2.4.7 - Focus Visible. We will fix this so the checkboxes have keyboard focus. We plan to fix this compliance issue by 31 July 2021.

On a page where we ask for a date, we use the wrong type of number input, which can cause issues when using certain devices. This fails WCAG 2.1: Understanding Success Criterion 4.1.2: Name, Role, Value. We will update this to use the right type of number input so users can give us the information without difficulty. We plan to fix this compliance issue by 31 July 2021.

On pages where we ask for an amount of money, we currently do not show the keyboard for numbers on a mobile device. This fails WCAG 2.1 - Understanding Success Criterion 4.1.2 - Name, Role, Value. We will update the service so a user can access those pages using a number keypad on mobile devices. We plan to fix this compliance issue by 31 July 2021.

On some pages there is no hint text to help users give the right information. This fails WCAG 2.1 - Understanding Success Criterion 3.3.2 - Labels or Instructions. We will add hint text to make it clear what users need to enter. We plan to fix this compliance issue by 31 July 2021.

On some pages, when using a screen reader users are given information that should be hidden, like spaces. This fails WCAG 2.1 - Understanding Success Criterion 4.1.1 - Parsing. We will fix this so users do not hear anything that is not useful or could be confusing. We plan to fix this compliance issue by 31 July 2021.

On some pages, we have boxes to add dates, and these are not read out right by a screen reader. This fails WCAG 2.1 - Understanding Success Criterion 4.1.2 - Name, Role, Value. We will fix this so these fields are read out correctly and users know how to interact with them. We plan to fix this compliance issue by 31 July 2021.

When there is focus on fields, radios and checkboxes in the service, the colour does not meet the minimum colour contrast. This fails WCAG 2.1 - Understanding Success Criterion 1.4.3 - Contrast (Minimum). We will fix this to make it easier for users to see where the focus is on the page. We plan to fix this compliance issue by 31 July 2021.

When there is focus on errors in the service, the colour does not meet the minimum colour contrast. This fails WCAG 2.1 - Understanding Success Criterion 1.4.3 - Contrast (Minimum). We will fix this to make it easier for users to see where the focus is on the page. We plan to fix this compliance issue by 31 July 2021.

Some of our error messages do not work properly which can cause issues for users. This fails WCAG 2.1 - Understanding Success Criterion 3.3.3 - Error Suggestion. We plan to fix this to make sure all our error messages make sense to users. We plan to fix this compliance issue by 31 July 2021.

When using a screen reader, there are some extra words being read out which make it difficult to follow the information on the page. This fails WCAG 2.1 - Making the text easier to read. We will fix this so the information is easier to read and understand. We plan to fix this compliance issue by 31 July 2021.

How we tested this service

The service was last tested on 14 September 2019 and was checked for compliance with WCAG 2.1 AA.

The service was built using parts that were tested by the Digital Accessibility Centre. The full service was tested by HMRC and included disabled users.

This page was published on 14 September 2019. It was last updated on 14 September 2019.

Get help with this page (opens in new tab)