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:

  • users of assistive technologies may have difficulty using the interactive tables
  • when using the interactive tables, screen reader users are not informed of important information when it becomes available
  • when using the interactive tables, some screen reader users may be unaware that filter options are available or having difficulty using them
  • screen reader users are unable to access an interactive table easily as it is not marked up as a standard HTML table
  • interactive tables are contained within an iframe that does not have a title attribute to describe its contents
  • the drill on option in interactive tables is not labelled, which may cause difficulty for some users of assistive technology
  • the filter options in interactive tables convey some information by colour alone
  • the purpose of the diamond-shaped symbol used in interactive tables is not explained
  • when subscribing to email alerts, the input field's aria-describedby attribute does not recognise the hint text id attribute value that it refers to
  • when subscribing to email alerts, input error messages are not accessible to screen readers users
  • when subscribing to or unsubscribing from email alerts, some pages do not include a language attribute, which means that screen reader software cannot identify the primary language of the page
  • when unsubscribing from email alerts, the code used on the page may cause issues for screen reader users
  • when unsubscribing from email alerts, the page content is not introduced by a heading
  • the homepage search feature may cause difficulty for voice activation users when trying to use standard voice commands
  • commodity code links on trader details pages are not accessible to keyboard commands
  • the CSV file of trader search results may cause difficulty for screen reader users when trying to navigate the table content
  • some pages do not have page titles that uniquely describe or introduce the content
  • some page elements on the register for Intrastat service have the same attribute id values, so may be being overlooked by some assistive technologies
  • some page elements of interactive tables are not highlighted by a visible focus indicator to help a user know clearly which element has the keyboard focus
  • when using the interactive tables, increasing text size can result in column headers being partly obscured by the data table
  • when the page is magnified to 400% and the width is set to 1280px, interactive tables do not enlarge, and the link to download search results in CSV format will require horizontal scrolling
  • when unsubscribing from email alerts, the focus indicator on buttons does not have sufficient colour contrast
  • when saving changes to cookie preferences, some screen reader users may not be aware of the success message

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

Users of assistive technologies may have difficulty using the interactive tables. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing) and 4.1.2 (Name, Role, Value) This will be fixed by 31 March 2023.

When using the interactive tables, screen reader users are not informed of important information when it becomes available. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships) This will be fixed by 31 March 2023.

When using the interactive tables, some screen reader users may be unaware that filter options are available or having difficulty using them. This does not meet WCAG 2.1 success criterion 2.4.3 (Focus Order) This will be fixed by 31 March 2023.

Screen reader users are unable to access an interactive table easily as it is not marked up as a standard HTML table. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships) This will be fixed by 31 March 2023.

Interactive tables are contained within an iframe that does not have a title attribute to describe its contents. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass Blocks) and 4.1.2 (Name, Role, Value) This will be fixed by 31 March 2023.

The drill on option in interactive tables is not labelled, which may cause difficulty for some users of assistive technology. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and (4.1.2 Name, Role, Value) This will be fixed by 31 March 2023.

The filter options in interactive tables convey some information by colour alone. This does not meet WCAG 2.1 success criterion 1.4.1 (Use of Color) This will be fixed by 31 March 2023.

The purpose of the diamond-shaped symbol used in interactive tables is only partially explained. This does not meet WCAG 2.1 success criterion 1.3.3 (Sensory Characteristics) This will be fixed by 31 March 2023.

When subscribing to email alerts, the input field's aria-describedby attribute does not recognise the hint text id attribute value that it refers to. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, Role, Value) This will be fixed by 31 March 2023.

When subscribing to email alerts, input error messages are not accessible to screen readers users. This does not meet WCAG 2.1 success criterion 3.3.1 (Error Identification) and 3.3.3 (Error Suggestion) This will be fixed by 31 March 2023.

When subscribing to or unsubscribing from email alerts, some pages do not include a language attribute, which means that screen reader software cannot identify the primary language of the page. This does not meet WCAG 2.1 success criterion 3.1.1 (Language of Page) This will be fixed by 31 March 2023.

When unsubscribing from email alerts, the code used on the page may cause issues for screen reader users. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships) This will be fixed by 31 March 2023.

When unsubscribing from email alerts, the page content is not introduced by a heading. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships) and 2.4.1 (Bypass Blocks) This will be fixed by 31 March 2023.

The homepage search feature may cause difficulty for voice activation users when trying to use standard voice commands. This does not meet WCAG 2.1 success criterion 2.5.3 (Label in Name) This will be fixed by 31 March 2023.

Commodity code links on trader details pages are not accessible to keyboard commands. This does not meet WCAG 2.1 success criterion 2.1.1 (Keyboard) This will be fixed by 31 March 2023.

The CSV file of trader search results may cause difficulty for screen reader users when trying to navigate the table content. This does not meet WCAG 2.1 success criterion 1.3.1 (Info and Relationships) This will be fixed by 31 March 2023.

Some pages do not have page titles that uniquely describe or introduce the content. This does not meet WCAG 2.1 success criterion 2.4.2 (Page Titled) This will be fixed by 31 March 2023.

Some page elements on the register for Intrastat service have the same attribute id values, so may be being overlooked by some assistive technologies. This does not meet WCAG 2.1 success criterion 4.1.1 (Parsing) This will be fixed by 31 March 2023.

Some page elements of interactive tables are not highlighted by a visible 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) This will be fixed by 31 March 2023.

When using the interactive tables, increasing text size can result in column headers being partly obscured by the data table. This does not meet WCAG 2.1 success criterion 1.4.12 (Text Spacing) This will be fixed by 31 March 2023.

When the page is magnified to 400% and the width is set to 1280px, interactive tables do not enlarge, and the link to download search results in CSV format will require horizontal scrolling. This does not meet WCAG 2.1 success criterion 1.4.10 (Reflow) This will be fixed by 31 March 2023.

When unsubscribing from email alerts, the focus indicator on buttons does not have sufficient colour contrast. This does not meet WCAG 2.1 success criterion 1.4.11 (Non-text Contrast) This will be fixed by 31 March 2023.

When saving changes to cookie preferences, some screen reader users may not be aware of the success message. This does not meet WCAG 2.1 success criterion 4.1.3 (Status Messages) This will be fixed by 31 March 2023.

How we tested this service

The service was last tested on 29 March 2021 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 23 March 2022.

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