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:

  • on the "Latest from UK Trade Info" page screen reader users will not hear information about the frequency of emails if they jump directly to the email field
  • on the "Overseas trade data table" page speech recognition users won't be able to fill the form without using a mouse-grid.
  • on the "Overseas trade data table" and the "Regional trade data table" pages the expand row option is not reachable via keyboard or exposed to screen-readers. Voice recognition users will need to use a mouse-grid to activate it.
  • on the "Overseas trade data table page" there is a context menu that is only available using a mouse.
  • on "Overseas trade by commodity code" and "Overseas trade by Standard International Trade Classification" pages have the same page title and heading, making it difficult to identify which page users on.
  • on the "Register to submit Intrastat declarations" page the page title does not describe what the user is registering for, so screen-reader users will need to check the heading.
  • on the "UK trader company name" page keyboard user won't be able to access the "Commodity Code" links
  • on the "Overseas trade data table" page the meaning of the icons next to the commodities is unclear
  • on the "Overseas trade data table" and "Regional trade data table" pages users with vision impairments may not be able to tell when a filter is enabled
  • on the "Overseas trade data table" and "Regional trade data table" pages screen-reader users will have difficulties with understanding and navigating the table content and might require assistance with it.
  • on the "Unsubscribe" page there are no headings, so screen-reader users will need to explore the content.
  • on the "Unsubscribe" page there is no main region so screen-reader users will need to explore the content.
  • on the "Help with using the new Trade Info website" page people with motor impairments will have difficulties with reading or being made aware of error messages for the email updates form.
  • on the "Overseas trade data table" page screen-reader users might be confused with a duplicated "Skip to the main content" button in the middle of the main content.
  • on the "Overseas trade data table" page screen-reader users won't be able to understand what each "Apply" button is related to when viewing them in an elements list
  • on the "Overseas trade data table" page people with vision and cognitive impairments will have difficulties with understanding and reading table content where text is too close to each other and some column headers are obstructed by the data table.
  • on the "Help with using the new UK Trade Info website" page screen-reader users on JAWS with IE11 or NVDA with Firefox won't be able to identify that they submitted cookie preferences successfully without checking the page for the success message.
  • on the "Unsubscribe" page people with vision impairments using a keyboard may not be able to identify if they are currently on the correct element.

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

Missing association between instruction and form elements. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value This will be fixed by 31 December 2021.

Incorrect implementation of form controls makes speech recognition users unable to interact with it using standard commands. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value and 4.1.1 Parsing This will be fixed by 31 December 2021.

Incorrect implementation doesn't allow keyboard users to interact with elements. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value and 4.1.1 Parsing This will be fixed by 31 December 2021.

Incorrect implementation of the expanded row prevents people from accessing it by keyboard and creates difficulties for screen reader and speech recognition users. This fails WCAG 2.1 success criterion 4.1.2 Name, Role, Value and 4.1.1 Parsing This will be fixed by 31 December 2021.

Identical page titles for different pages cause difficulties for users to identify which page they are on. This fails WCAG 2.1 success criterion 2.4.2 Page Titled This will be fixed by 31 December 2021.

Page title doesn't provide enough information for screen reader users about page content. This fails WCAG 2.1 success criterion 2.4.2 Page Titled This will be fixed by 31 December 2021.

"Commodity Code" links removed from tab order making it not accessible by keyboard users. This fails WCAG 2.1 success criterion 2.1.1 Keyboard This will be fixed by 31 December 2021.

Icons don't provide additional information make it hard for some users to understand what they represent. This fails WCAG 2.1 success criterion 1.3.3 Sensory Characteristics This will be fixed by 31 December 2021.

Status of the "Apply" button relies only on colour which is hard to distinguish for people with visual impairments. This fails WCAG 2.1 success criterion 1.4.1 Use of Color This will be fixed by 31 December 2021.

Incorrect implementation of table content makes it hard for screen reader users to navigate and orient themselves. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships This will be fixed by 31 December 2021.

Missing headings on the page makes it hard for screen reader users to navigate and understand the page. This fails WCAG 2.1 success criterion 1.3.1 Info and Relationships and 2.4.1 Bypass Blocks This will be fixed by 31 December 2021.

Error messages not usable by people with motor impairments, when the focus shifts to another element error message disappear. This fails WCAG 2.1 success criterion 3.3.3 Error Suggestion This will be fixed by 31 December 2021.

Nested in the main region "Skip to main content" button creates confusion for screen reader users and might disorient them. This fails WCAG 2.1 success criterion 2.4.6 Headings and Labels This will be fixed by 31 December 2021.

"Apply" buttons additional information don't provide clarity for screen reader users what they are related to. This fails WCAG 2.1 success criterion 2.4.6 Headings and Labels This will be fixed by 31 December 2021.

Columns don't have enough spacing in between and column headings not fully visible. This fails WCAG 2.1 success criterion 1.4.12 Text Spacing This will be fixed by 31 December 2021.

Success message not determined correctly by JAWS with IE11 or NVDA with Firefox. This fails WCAG 2.1 success criterion 4.1.3 Status Messages This will be fixed by 31 December 2021.

Focus indicators do not have sufficient contrast. This fails WCAG 2.1 success criterion 1.4.11 Non-text Contrast This will be fixed by 31 December 2021.

How we tested this service

The service was last tested on 29 March 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 19 October 2020. It was last updated on 6 April 2021.

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