Skip to main content

Accessibility statement

This statement applies to MTD Gateway at mtdgateway.co.uk, including the signed-in parts of the service. It does not cover HMRC's own pages, which you are sent to when you connect your HMRC account. HMRC publishes its own accessibility statement for those.

How accessible this service is meant to be

We want as many people as possible to be able to use this service. We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA.

The service is built with the GOV.UK Design System, which is designed and tested for accessibility. That means you should be able to:

  • change colours, contrast levels and fonts using your browser or operating system
  • zoom in up to 300% without text spilling off the screen
  • navigate the whole service using just a keyboard
  • listen to the service using a screen reader

We use the Design System's error summary pattern, so validation problems are announced and each message links to the field it belongs to, and we keep to one main thing per page.

How accessible this service actually is

Warning This service has been tested automatically and by keyboard, but it has not yet been tested with a screen reader or by disabled users. We believe it meets WCAG 2.2 level AA, but we have not proved it, so we do not yet claim full compliance.

Using the GOV.UK Design System gets us a long way, but it does not by itself make a service accessible. The parts we have built on top of it, in particular the CSV import screen, the transactions table and the submissions table, have had automated and keyboard testing only.

Audit results

We tested the service on 25 July 2026, in-house, using the axe accessibility engine against WCAG 2.2 level A and AA, on all 23 pages of the service including every signed-in page and the agent pages. We also checked keyboard navigation by hand, and checked that every page works at a 320 pixel width without sideways scrolling.

These are the problems we found, and what we did about them:

  • Every page reported the same title, so people using a screen reader or several browser tabs could not tell them apart. This failed WCAG 2.4.2 Page Titled (level A). Fixed. Each page now has its own title.
  • There was no "Skip to main content" link, so anyone using a keyboard had to tab through the whole header on every page. Fixed. A skip link is now the first thing you reach, and it moves focus into the main content.
  • Several forms moved focus into the first field as the page loaded, which skipped the page heading and the skip link. Fixed. Pages now start at the top.
  • On the home page, the banner at the top sat outside the main content landmark, so people navigating by landmark could miss it. Fixed.
  • Moving between pages changed nothing a screen reader could hear, because this part of the service does not reload the page when you navigate. Fixed. Moving to a new page now moves you to the top of its content, so it is read out.
  • Every signed-in page needed sideways scrolling on a small phone, at a 320 pixel width. This failed WCAG 1.4.10 Reflow (level AA). Fixed. Tables now scroll within their own area, which you can reach by keyboard, instead of stretching the page.

After those fixes, automated testing reports no failures on any page. Automated testing typically finds only about a third of accessibility problems, so this is not the same as the service being accessible.

What we have not tested yet

  • testing with screen readers such as NVDA, JAWS or VoiceOver
  • testing with speech recognition software or screen magnification
  • testing with disabled people, rather than with tools
  • an independent audit by an accessibility specialist

Until those are done, please tell us if you hit a problem. We will fix it and say so here.

Reporting an accessibility problem

If you find a problem, or you need information from this service in a different format, email support@mtdgateway.co.uk.

Tell us:

  • the web address of the page
  • what you were trying to do
  • what happened, and what you expected to happen
  • the browser, device and any assistive technology you were using

We treat accessibility reports as faults in the service. We will confirm we have received your report, tell you what we are going to do about it, and give you the information you asked for in another way in the meantime.

How we will prepare the full statement

Once testing is complete we will replace the audit section above with the findings. Our plan is an automated check of every page, both public and signed in, a keyboard-only walkthrough of the main journeys, and a screen reader check of the forms and tables.

Last updated: 25 July 2026