Accessibility statement for UK Trade Info 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 UK Trade Info service, available at https://www.uktradeinfo.com/home.

Using this service

UK Trade Info publishes detailed UK trade data and statistical information produced by HM Revenue and Customs (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 feedback form, dropdown menus below search fields, and Intrastat services have not been tested for accessibility issues
  • some pages may be difficult for assistive technologies to parse because of an incorrect meta element
  • on pages with Related content sections, the navigation elements do not all have unique labels, which may make navigating the page difficult
  • on the Privacy page, there is no visible keyboard focus on links in the main content
  • screen readers users may have difficulty using the breadcrumb trail navigation displayed on some pages
  • top navigation links do not indicate to screen reader users which section they are currently in
  • on some pages, screen readers users will hear the same text repeated for the search heading and label
  • on the Find commodity data page, the code used for the Related content section may cause issues for screen readers users
  • the Bulk datasets guidance and technical specifications page contains repeated text, which may cause issues for screen reader users
  • the main content of the Bulk datasets guidance and technical specifications page does not have hierarchical headings and subheadings
  • search fields do not have a search role on the heading to identify the section
  • some search fields do not correctly identify the type of input required
  • some pages have skipped heading levels, which could be confusing for users of assistive technologies
  • some page titles do not match the page heading
  • some pages have a missing or incorrect aria-controls attribute or empty aria-live attribute
  • on the homepage, images and link text do not appear in high contrast for the items under Featured, and the keyboard focus (the vertical white line) is partly displayed
  • the pagination of search results pages may be confusing for users of screen readers
  • the filename of the trader search results and data tables CSV file is always the same when downloading results, which may be confusing for users
  • some pages have a missing or incorrect aria-controls attribute or empty aria-live attribute
  • the fieldset for filtering trader search results by trader type has a missing legend to describe the purpose of the radio buttons
  • company details pages have a duplicate class attribute
  • on search results pages, the purpose of the Traders search type link is not obvious
  • some links do not have unique accessible names to allow users of screen readers to distinguish them
  • some of the links in the website are not descriptive
  • on search results pages, the error message when no text is entered does not match the hint text page on the page
  • on some pages, error messages are not differentiated from other text when viewing in greyscale
  • commodity details pages have multiple heading level 1 tags
  • on pages with Related content sections, the Related content heading level 2 tag should be within the nav element to define the relationship and allow screen readers to bypass it
  • on the Find commodity data page, the search heading and label are not wrapped in the search role to identify the section
  • commodity codes shown in search results and commodity details pages are read out as individual digits for users of screen readers
  • trying to search without entering any text into the search field may cause an error in the service
  • search result pages may be difficult for assistive technologies to parse because of incorrect markup. compliance issue by 31 December 2020
  • on search results pages, aria-label is used on an element that does not reliably convey this attribute
  • links in search results are not read out as a single link with a screen reader on mobile devices, which makes the information hard to follow
  • the error message displayed when trying to search without entering any search term is not associated with the input field
  • screen reader users may have difficulty using the interactive data tables
  • data tables are not introduced with a heading to help screen reader users to know what the main topic of the page is
  • the icon used to expand down one level in a hierarchy in data tables is not labelled, and the expand and collapse icons in the grid do not have accessible names, which may cause difficulties for screen reader users
  • text size in data tables does not increase with zoom or font size
  • keyboard users will not be able to access all of the functionality of the interactive data tables
  • keyboard users are not able to navigate to content below interactive data tables
  • there are 2 aria-labels for the main navigation, which may cause difficulty for screen reader users
  • the pages titles of data tables include acronyms that are not well known
  • data tables may be difficult to use with Voice Over on iOS
  • when changing the inputs on data tables, users are not alerted of a change in the grid
  • using the context menu on data tables may cause difficulties for screen reader users
  • the guide to using data tables is not linked to at the beginning of the page
  • the link provided on selecting Share or link to this table is not visible and alerted to screen readers
  • the input to share or link to a table does not have a label describing its purpose and is not updating when changing data
  • data table grids do not have an accessible name describing their purpose, which may cause difficulties for screen reader users
  • the Cookies we use on UK Trade Info page does not use captions on tables to help screen reader users to identify the table
  • the table headings on the Cookies we use on UK Trade Info page are not announced when using the table shortcut keys in NVDA on Firefox
  • selecting Accept all cookies on all pages and Save changes on the Set your cookie preferences for UK Trade Info page does not alert screen reader users using JAWS on Internet Explorer 11 and NVDA on Firefox
  • the Set your cookie preferences page for UK Trade Info contains a code error
  • the Set cookie preferences button does not have Javascript polyfill to make sure it acts like a button
  • the Latest from UK Trade Info page may cause difficulties for screen reader users when navigating the list of news articles
  • when tabbing on the unsubscribe from email alerts page, a subtle focus is displayed on the buttons which can cause disorientation
  • when subscribing to or unsubscribing email alerts, the code used on the page may cause issues for users of assistive technologies
  • subscribing to email alerts uses an iframe that does not have a title to describe its purpose, which may cause difficulty for screen reader users
  • the titles of the subscribe to or unsubscribe from email alerts pages do not identify these as being part of the UK Trade Info website
  • callout boxes used on some pages do not meet the required contrast ratio of 4.5:1 between text and the background behind the text
  • some pages do not have breadcrumb trail navigation
  • on the homepage, the links See all news and See all statistical releases do not have sufficient spacing between them, making the links difficult to read and comprehend
  • search results are not introduced by a heading
  • when larger text is set on iOS, the menu button is displayed behind the service name
  • parts of the data tables interface does not have sufficient colour contrast against the background
  • 400% zoom causes the drill options in data tables to overlap
  • the data tables do not have a consistent keyboard focus indicator to help a user know clearly which element has the keyboard focus
  • on the cookie banner, the purpose of the "Hide" button (styled as a link) is ambiguous for screen reader users when using shortcut keys
  • when subscribing to email alerts, the email address field does not have the spellcheck attribute set to false so that browsers do not spell-check the email address. Also, the autocomplete attribute is not set to email so that browsers can fill in the email address automatically. The hint text for the field has not been associated using aria-describedby
  • the message displayed when a user is already signed up to email alerts does not have enough contrast for users with moderately low vision to read it without contrast-enhancing technology
  • when subscribing to or unsubscribing from email alerts, increasing the font size of the page does not increase the text size
  • when subscribing to or unsubscribing from to email alerts, some pages do not have heading level 1 tags or references to UKTi Trade Info to help users understand what the pages contain
  • when subscribing to email alerts, the email address field uses client-side validation built into browsers to check for correct input, which has usability and accessibility issues
  • when subscribing to email alerts, some screen reader users are not made aware of the success message or if they have already subscribed

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

Some pages may be difficult for assistive technologies to parse because of an incorrect meta element. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

On pages with Related content sections, the navigation elements do not all have unique labels, which may make navigating the page difficult. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

On the Privacy page, there is no visible keyboard focus on links in the main content. This does not meet WCAG 2.1 success criterion 2.4.7 (Focus Visible). We plan to fix this compliance issue by 31 December 2020.

Screen readers users may have difficulty using the breadcrumb trail navigation displayed on some pages. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Top navigation links do not indicate to screen reader users which section they are currently in. This does not meet WCAG 2.1 success criterion 1.3.3 (Sensory Characteristics). We plan to fix this compliance issue by 31 December 2020.

On some pages, screen readers users will hear the same text repeated for the search heading and label. This does not meet WCAG 2.1 success criterion 3.3.2 (Labels or Instructions). We plan to fix this compliance issue by 31 December 2020.

On the Find commodity data page, the code used for the Related content section may cause issues for screen readers users. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to fix this compliance issue by 31 December 2020.

The Bulk datasets guidance and technical specifications page contains repeated text, which may cause issues for screen reader users. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value) and 2.4.4 (Link Purpose (in Context)). We plan to fix this compliance issue by 31 December 2020.

The main content of the Bulk datasets guidance and technical specifications page does not have hierarchical headings and subheadings. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Search fields do not have a search role on the heading to identify the section. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to fix this compliance issue by 31 December 2020.

Some search fields do not correctly identify the type of input required. This does not meet WCAG 2.1 success criterion 3.3.2 (Labels or Instructions). We plan to fix this compliance issue by 31 December 2020.

Some pages have skipped heading levels, which could be confusing for users of assistive technologies. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Some page titles do not match the page heading. This does not meet WCAG 2.1 success criterion 2.4.2 (Page Titled). We plan to fix this compliance issue by 31 December 2020.

Some pages have a missing or incorrect aria-controls attribute or empty aria-live attribute . This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

On the homepage, images and link text do not appear in high contrast for the items under Featured, and the keyboard focus (the vertical white line) is partly displayed. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

The pagination of search results pages may be confusing for users of screen readers. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

The filename of the trader search results and data tables CSV file is always the same when downloading results, which may be confusing for users. This does not meet WCAG 2.1 success criterion 2.4.2 (Page Titled). We plan to fix this compliance issue by 31 December 2020.

Some pages have a missing or incorrect aria-controls attribute or empty aria-live attribute . This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

The fieldset for filtering trader search results by trader type has a missing legend to describe the purpose of the radio buttons. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to fix this compliance issue by 31 December 2020.

Company details pages have a duplicate class attribute. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

On search results pages, the purpose of the Traders search type link is not obvious. This does not meet WCAG 2.1 success criterion 2.4.4 (Link Purpose (in Context)). We plan to fix this compliance issue by 31 December 2020.

Some links do not have unique accessible names to allow users of screen readers to distinguish them. This does not meet WCAG 2.1 success criterion 2.4.4 (Link Purpose (in Context)). We plan to fix this compliance issue by 31 December 2020.

Some of the links in the website are not descriptive. This does not meet WCAG 2.1 success criterion 2.4.4 (Link Purpose (in Context)). We plan to fix this compliance issue by 31 December 2020.

On search results pages, the error message when no text is entered does not match the hint text page on the page. This does not meet WCAG 2.1 success criterion 3.3.1 (Error Identification). We plan to fix this compliance issue by 31 December 2020.

On some pages, error messages are not differentiated from other text when viewing in greyscale. This does not meet WCAG 2.1 success criterion 3.3.1 (Error Identification). We plan to fix this compliance issue by 31 December 2020.

Commodity details pages have multiple heading level 1 tags. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to fix this compliance issue by 31 December 2020.

On pages with Related content sections, the Related content heading level 2 tag should be within the nav element to define the relationship and allow screen readers to bypass it. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to fix this compliance issue by 31 December 2020.

On the Find commodity data page, the search heading and label are not wrapped in the search role to identify the section. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to fix this compliance issue by 31 December 2020.

Commodity codes shown in search results and commodity details pages are read out as individual digits for users of screen readers. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Trying to search without entering any text into the search field may cause an error in the service. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

Search result pages may be difficult for assistive technologies to parse because of incorrect markup. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

On search results pages, aria-label is used on an element that does not reliably convey this attribute. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to fix this compliance issue by 31 December 2020.

Links in search results are not read out as a single link with a screen reader on mobile devices, which makes the information hard to follow. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

The error message displayed when trying to search without entering any search term is not associated with the input field. This does not meet WCAG 2.1 success criterion 3.3.1 (Error Identification). We plan to fix this compliance issue by 31 December 2020.

Screen reader users may have difficulty using the interactive data tables. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Data tables are not introduced with a heading to help screen reader users to know what the main topic of the page is. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

The icon used to expand down one level in a hierarchy in data tables is not labelled, and the expand and collapse icons in the grid do not have accessible names, which may cause difficulties for screen reader users. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Text size in data tables does not increase with zoom or font size. This does not meet WCAG 2.1 success criterion 1.4.4 (Resize text). We plan to fix this compliance issue by 31 December 2020.

Keyboard users will not be able to access all of the functionality of the interactive data tables. This does not meet WCAG 2.1 success criterion 2.1.1 (Keyboard). We plan to fix this compliance issue by 31 December 2020.

Keyboard users are not able to navigate to content below interactive data tables. This does not meet WCAG 2.1 success criterion 2.1.2 (No Keyboard Trap). We plan to fix this compliance issue by 31 December 2020.

There are 2 aria-labels for the main navigation, which may cause difficulty for screen reader users. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks). We plan to fix this compliance issue by 31 December 2020.

The pages titles of data tables include acronyms that are not well known. This does not meet WCAG 2.1 success criterion 2.4.2 (Page Titled). We plan to fix this compliance issue by 31 December 2020.

Data tables may be difficult to use with Voice Over on iOS. This does not meet WCAG 2.1 success criterion 2.5.1 (Pointer Gestures). We plan to fix this compliance issue by 31 December 2020.

When changing the inputs on data tables, users are not alerted of a change in the grid. This does not meet WCAG 2.1 success criterion 3.2.2 (On Input). We plan to fix this compliance issue by 31 December 2020.

Using the context menu on data tables may cause difficulties for screen reader users. This does not meet WCAG 2.1 success criterion 3.2.2 (On Input). We plan to fix this compliance issue by 31 December 2020.

The guide to using data tables is not linked to at the beginning of the page. This does not meet WCAG 2.1 success criterion 3.2.2 (Labels Or Instructions). We plan to fix this compliance issue by 31 December 2020.

The link provided on selecting Share or link to this table is not visible and alerted to screen readers. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to fix this compliance issue by 31 December 2020.

The input to share or link to a table does not have a label describing its purpose and is not updating when changing data. This does not meet WCAG 2.1 success criterion 3.2.2 (Labels Or Instructions). We plan to fix this compliance issue by 31 December 2020.

Data table grids do not have an accessible name describing their purpose, which may cause difficulties for screen reader users. This does not meet WCAG 2.1 success criterion 3.2.2 (Labels Or Instructions). We plan to fix this compliance issue by 31 December 2020.

The Cookies we use on UK Trade Info page does not use captions on tables to help screen reader users to identify the table. This does not meet WCAG 2.1 success criterion Understanding Success Criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

The table headings on the Cookies we use on UK Trade Info page are not announced when using the table shortcut keys in NVDA on Firefox. This does not meet WCAG 2.1 success criterion Understanding Success Criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

Selecting Accept all cookies on all pages and Save changes on the Set your cookie preferences for UK Trade Info page does not alert screen reader users using JAWS on Internet Explorer 11 and NVDA on Firefox. This does not meet WCAG 2.1 success criterion 3.3.1 (Error Identification). We plan to fix this compliance issue by 31 December 2020.

The Set your cookie preferences page for UK Trade Info contains a code error. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

The Set cookie preferences button does not have Javascript polyfill to make sure it acts like a button. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to fix this compliance issue by 31 December 2020.

The Latest from UK Trade Info page may cause difficulties for screen reader users when navigating the list of news articles. This does not meet WCAG 2.1 success criterion Understanding Success Criterion 1.3.1 (Info and Relationships). We plan to fix this compliance issue by 31 December 2020.

When tabbing on the unsubscribe from email alerts page, a subtle focus is displayed on the buttons which can cause disorientation. This does not meet WCAG 2.1 success criterion 2.4.7 (Focus Visible). We plan to fix this compliance issue by 31 December 2020.

When subscribing to or unsubscribing email alerts, the code used on the page may cause issues for users of assistive technologies. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing). We plan to fix this compliance issue by 31 December 2020.

Subscribing to email alerts uses an iframe that does not have a title to describe its purpose, which may cause difficulty for screen reader users. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value). We plan to fix this compliance issue by 31 December 2020.

The titles of the subscribe to or unsubscribe from email alerts pages do not identify these as being part of the UK Trade Info website. This does not meet WCAG 2.1 success criterion 2.4.2 (Page Titled). We plan to fix this compliance issue by 31 December 2020.

Callout boxes used on some pages do not meet the required contrast ratio of 4.5:1 between text and the background behind the text. This does not meet WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)). We plan to fix this compliance issue by 31 December 2020.

Some pages do not have breadcrumb trail navigation. This does not meet WCAG 2.1 success criterion 3.2.3 (Consistent Navigation). We plan to fix this compliance issue by 31 December 2020.

On the homepage, the links See all news and See all statistical releases do not have sufficient spacing between them, making the links difficult to read and comprehend. This does not meet WCAG 2.1 success criterion 1.4.12 (Text Spacing). We plan to fix this compliance issue by 31 December 2020.

Search results are not introduced by a heading. This does not meet WCAG 2.1 success criterion 2.4.6 (Headings and Labels). We plan to fix this compliance issue by 31 December 2020.

When larger text is set on iOS, the menu button is displayed behind the service name. This does not meet WCAG 2.1 success criterion 1.4.4 (Resize text). We plan to fix this compliance issue by 31 December 2020.

Parts of the data tables interface does not have sufficient colour contrast against the background. This does not meet WCAG 2.1 success criterion 1.4.3 Contrast (Minimum). We plan to fix this compliance issue by 31 December 2020.

400% zoom causes the drill options in data tables to overlap. This does not meet WCAG 2.1 success criterion 1.4.10 (Reflow). We plan to fix this compliance issue by 31 December 2020.

The data tables do not have a consistent keyboard focus indicator to help a user know clearly which element has the keyboard focus. This does not meet WCAG 2.1 success criterion 2.4.7 (Focus Visible). We plan to fix this compliance issue by 31 December 2020.

On the cookie banner, the purpose of the "Hide" button (styled as a link) is ambiguous for screen reader users when using shortcut keys. This does not meet WCAG 2.1 success criterion Understanding Success Criterion 2.4.6 ( Headings and Labels). We plan to fix this compliance issue by 31 December 2020.

When subscribing to email alerts, the email address field does not have the spellcheck attribute set to false so that browsers do not spell-check the email address. Also, the autocomplete attribute is not set to email so that browsers can fill in the email address automatically. The hint text for the field has not been associated using aria-describedby. This does not meet WCAG 2.1 success criterion Understanding Success Criterion 1.3.5 (Identify Input Purpose). We plan to fix this compliance issue by 31 December 2020.

The message displayed when a user is already signed up to email alerts does not have enough contrast for users with moderately low vision to read it without contrast-enhancing technology. This does not meet WCAG 2.1 success criterion 1.4.3 (Contrast (Minimum)). We plan to fix this compliance issue by 31 December 2020.

When subscribing to or unsubscribing from email alerts, increasing the font size of the page does not increase the text size. This does not meet WCAG 2.1 success criterion 1.4.4 (Resize text). We plan to fix this compliance issue by 31 December 2020.

When subscribing to or unsubscribing from to email alerts, some pages do not have heading level 1 tags or references to UKTi Trade Info to help users understand what the pages contain. This does not meet WCAG 2.1 success criterion 2.4.6 (Headings and Labels). We plan to fix this compliance issue by 31 December 2020.

When subscribing to email alerts, the email address field uses client-side validation built into browsers to check for correct input, which has usability and accessibility issues. This does not meet WCAG 2.1 success criterion 3.3.3 (Error Suggestion). We plan to fix this compliance issue by 31 December 2020.

When subscribing to email alerts, some screen reader users are not made aware of the success message or if they have already subscribed. This does not meet WCAG 2.1 success criterion 4.1.3 (Status Messages). We plan to fix this compliance issue by 31 December 2020.

How we tested this service

The service was last tested on 10 November 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 published on 19 October 2020. It was last updated on 17 November 2020.

Get help with this page (opens in new tab)