Accessibility statement for VAT Flat Rate Scheme 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 VAT Flat Rate Scheme service, available at https://www.tax.service.gov.uk/check-your-vat-flat-rate/vat-return-period.

Using this service

The VAT FRS calculator allows you to work out if you have a limited cost business and are eligible for the VAT Flat Rate Scheme. This scheme allows you to pay a fixed rate of VAT to HMRC.

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:

  • the menu toggle in the banner on a small screen disappears when clicked.
  • ”Home” navigation option is not selected using a voice command.
  • some elements present that had a colour used for styling focus indication that did not pass the expected ratio.
  • page <title> does not follow pattern.
  • error page title is the same as the original page title.
  • no keyboard focus on buttons in high contrast mode.
  • combine heading and label to reduce noise for screen reader and add/associate hint.
  • error messages are not associated to inputs.
  • single input therefore a <legend> is not required.
  • duplicate “class” attribute causing HTML error.
  • the value of the “for” attribute of the “label” element must be the ID of a non-hidden form control.
  • incorrect spelling of class attribute.

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.

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

The menu toggle in the banner on a small screen disappears when clicked. Also, when JS is disabled, the menu toggle is not hidden. This doesn’t meet WCAG 2.1 success criteria 1.3.1 (info and relationships). This will be fixed by 16 October 2022.

“Home” navigation option is not selected using a voice command as it's getting confused with the browser home button or device home button. This doesn’t meet WCAG 2.1 success criteria 2.4.4 (link purpose in context). This will be fixed by 16 October 2022.

The colour of the focus indicator used throughout the service failed to meet the expected ratio of 3:1 to pass WCAG 2.1 success criteria 1.4.11 Non-text Contrast AA and may prove difficult for some users to perceive. This doesn’t meet WCAG 2.1 success criteria 1.4.11 (non-text contrast). This will be fixed by 16 October 2022.

Page title pattern should be: h1 - service name - GOV.UK. This doesn’t meet WCAG 2.1 success criteria 2.4.2: (page titled). This will be fixed by 16 October 2022.

When there is an error on the page, add Error: to the beginning of the page <title> so screen readers read it out as soon as possible. This doesn’t meet WCAG 2.1 success criteria 2.4.2: (page titled). This will be fixed by 16 October 2022.

There’s no keyboard focus on any radio button when in high contrast mode. This doesn’t meet WCAG 2.1 success criteria 2.4.7 (focus visible). This will be fixed by 16 October 2022.

There is only a single input on this page so a fieldset/legend is not required. Combine the heading and label tags so that screen reader users do not hear the same copy repeated more than necessary. This doesn’t meet WCAG 2.1 success criteria 3.3.2: (labels or instructions). This will be fixed by 16 October 2022.

The error message should be associated to the inputs/fieldsets using aria-describedby and prepended with visually hidden text Error: on error pages for the benefit of screen readers. This doesn’t meet WCAG 2.1 success criteria 3.3.2: (labels or instructions). This will be fixed by 16 October 2022.

There is only a single input on this page so a fieldset/legend is not required. This doesn’t meet WCAG 2.1 success criteria 3.3.2: (labels or instructions). This will be fixed by 16 October 2022.

Duplicate attribute “class”. This doesn’t meet WCAG 2.1 success criteria 4.1.1 (parsing). This will be fixed by 16 October 2022.

The value of the “for” attribute of the “label” element must be the ID of a non-hidden form control. This doesn’t meet WCAG 2.1 success criteria 4.1.1 (parsing). This will be fixed by 16 October 2022.

Attribute “clas” not allowed on element “div” at this point: This doesn’t meet WCAG 2.1 success criteria 4.1.1 (parsing). This will be fixed by 16 October 2022.

How we tested this service

The service was last tested on 16 October 2020 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 prepared on 21 September 2020. It was last updated on 21 September 2020.

Is this page not working properly? (opens in new tab)