Accessibility statement

This accessibility statement applies to content published on the Manage your vehicle testing service. This website is run by the Driver and Vehicle Standards Agency .

How you should be able to use this website

We want as many people as possible to be able to use this website. For example, this means you should be able to:

change colours, contrast levels and fonts using browser or device settings
zoom in up to 400% without the text spilling off the screen
navigate most of the website using a keyboard or speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We also make the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

Parts of this website are not fully accessible. For example:

some heading elements are not consistent
some page titles and headings are not consistent
some interactive elements are not accurately labelled
some pages are difficult to navigate using a keyboard
some focused elements have poor colour contrast
some documents are in PDF format and are not accessible

Feedback and contact information

Tell us if you need information in a different format.

In your message, include:

the web address (URL) of the content
your email address and name
the format you need - for example, plain text, braille, BSL, large print or audio CD

We’ll ask you how you want us to send messages or documents to you.

You can also view the organisation’s accessible document policy to report any problems or request documents in an alternative format.

Contacting us by phone or in person

We provide a text relay service for people who are deaf, hearing impaired or have a speech impediment. Our offices have audio induction loops, or if you contact us before your visit, we can arrange a British Sign Language (BSL) interpreter to help you complete the service in person.

Reporting accessibility problems with this website

If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements, contact us.

Enforcement procedure

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’re not happy with how we respond to your complaint, you can contact the Equality Advisory and Support Service (EASS) .

Technical information about this website’s accessibility

The Driver and Vehicle Standards Agency is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

On some pages, skip to main content links do not skip straight to the main content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
Some checkboxes are not accurately labelled. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Some decorative images are not hidden from screen reading software. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
Some pages contain duplicate id values. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
Some pages contain legend, table or form elements without a descriptive label. This means that some context will be missing for screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Some pages contain form elements without a unique descriptive label. This means that screen reader users cannot differentiate between different forms. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Some pages contain multiple main landmarks. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
On some pages, focus order does not follow a logical sequence. This fails WCAG 2.2 success criterion 2.4.3 (Focus Order).
Some ARIA roles are not accurate or contain invalid values. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
Some pages are submitted automatically when the user inputs a value. This fails WCAG 2.2 success criterion 3.2.2 (On Input).
Some headings are not accurately labelled to reflect their styling or function. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
Some page titles are not uniquely descriptive of the page content. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
On some pages, the colour contrast of focused elements fails to meet an accessible contrast ratio. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).
Some autocomplete attributes are not valid values. This fails WCAG 2.2 success criterion 1.3.5 Identify (Input Purpose).
On some pages, content can only be viewed by scrolling in two dimensions when using reflow. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
Some status messages do not have an assigned role. This means that they are not read out to screen reader users when they appear. This fails WCAG 2.2 success criterion 4.1.3 (Status Messages).
On some pages, adjusting the text spacing can cause text to become obscured or difficult to read. This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing).

Many documents are in non-HTML formats, for example PDF. They are not accessible in a number of ways including missing text alternatives and missing document structure.

Content that’s not within the scope of the accessibility regulations

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

What we are doing to improve accessibility

We are working with the Digital Accessibility Centre to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.

We will contact our payment and authentication providers to advise them of non-compliant areas of their technologies, to determine whether or not these issues can be fixed.

Preparation of this accessibility statement

This statement was prepared on 18 July 2022. It was last reviewed on 28 November 2025.

This website was last tested in September 2025 against the WCAG 2.2 AA standard. This test of a representative sample of pages was carried out by the Digital Accessibility Centre (DAC).

We also used findings from our own testing when preparing this accessibility statement.