Accessibility statement for Take a registration number off a vehicle (retain)
This accessibility statement applies to https://www.gov.uk/personalised-vehicle-registration-numbers/take-private-number-off.
This website is run by Driver and Vehicle Licensing Agency (DVLA). We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made 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
We know some parts of this website are not fully accessible:
- Some form elements do not have an associated label which will cause difficulties for screen reader users, as well as not being accessible to Voice Activation users through standard voice commands.
- There is some instance of incorrectly marked up headings; making it difficult for screen reader users to understand the structure of the page, as well as being able to clearly identify the contents of the page.
- Layers are not marked up correctly making it difficult for screen reader users.
- Some instances of colour used to indicate interactive content may cause users with low vision difficulty interacting with this content
- Some instances of lack of focus highlighting which may impact Mobility impaired
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
Email our External Communications team and we will see if we can help, or contact our Contact Centre via
Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: The Vehicles Service Manager Anthony.bamford@dvla.gov.uk
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, contact the Equality Advisory and Support Service (EASS).
Technical information about this website’s accessibility
Driver and Vehicle Licensing Agency (DVLA) 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.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 images do not have clear alternative text to describe their purpose, this is also present within the PDF document, so some screen reader users will have difficulty accessing the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by May 2021. When we publish new content we’ll make sure our use of images meets accessibility standards.
- Some pages are missing level 1 headings, don’t have a primary language set and unclear labelling which will make it difficult for screen reader users to understand the meaning and layout of the pages, load the correct pronunciation and identifying the purpose of some fields requiring completion. These instances fail WCAG 2.1 success criterion 1.3.1 (info and relationships).
We plan to add level 1 headings, set a primary language and labelling to all pages and documents by May 2021. When we publish new content we’ll make sure the use of labelling, headings and languages meet accessibility standards.
- Some links which offer expandable information do not announce if the information has been expanded or collapsed, this may be difficult for screen reader users as there is a lack of awareness of what the link does upon activation. These instances fail WCAG 2.1 success criterion 1.3.3 (sensory characteristics)
We plan to ensure all links that offer expanded text is clearly announced by May 2021. When we publish new content we’ll make sure the use of expandable text meets accessibility standards.
- Some text fails to meet WCAG standards for contrast which can make it difficult for low vision users. These instances fail WCAG 2.1 success criterion 1.4.3 (contrast minimum).
We plan to make changes so that all contrast throughout the site adheres to WGAC 2.1 by May 2021. When we publish new content we’ll make sure all text meets the contrast ratio standard of 4.5:1
- Non text contrast does not meet standards, keyboard users with visual deficiencies may experience difficulties to see the focus outline. These instances fail WCAG 2.1 success criterion 1.4.11 (Non-text Contrast)
We plan to make changes so that all non-text contrast throughout the site adheres to WGAC 2.1 by May 2021. When we publish non-text content we’ll make sure it has a contrast ratio of at least 3:1 against adjacent colour(s).
- Some icons used for information do not receive focus, which can present issues for keyboard only users. These instances fail WCAG 2.1 success criterion 2.1.1 (Keyboard)
We plan to make changes to all icons by introducing clear focus so that the site meets WGAC 2.1 by May 2021. When we use icons we’ll make sure it meets accessibility standards.
- Some content is only accessible to mouse users. These instances fail WCAG 2.1 success criterion 2.1.3 (Keyboard – No exceptions)
We plan to make the site accessible for all users including keyboard only by May 2021. When we publish new content we’ll make sure the it meets accessibility standards.
- Skipping content is not easy on all pages and documents These instances fail WCAG 2.1 success criterion 2.4.1 (Bypass blocks)
We plan to make sure every page is easy to navigate especially when skipping information by May 2021. When we publish new content we’ll make sure it meets the accessibility standards.
- When modals are presented the user can navigate outside of it without having to close the modal, this can cause confusion for screen reader users as structure and content become difficult to navigate. These instances fail WCAG 2.1 success criterion 2.4.3 (Focus order).
We plan to make changes to all modals within the site so that when opened you cannot navigate outside of the Modal without closing the content by May 2021. When we use models we’ll make sure they meet accessibility standards.
- There is an instance of an image link that has not been given clear alternative text which is not accessible for screen reader users. These instances fail WCAG 2.1 success criterion 2.4.4 (Link Purpose).
We plan to make sure all links have clear alternative text by May 2021. When we publish new content we’ll make sure it meets accessibility standards.
- Some download files do not contain file type within the link text, screen reader users will be unaware of software required to open documents also a modal within the payment screens does not contain a heading which gives screen reader users no context to the modal and its purpose. These instances fail WCAG 2.1 success criterion 2.4.6 (Headings and Labels).
We plan to make sure all download files, modals and links have clear headings by May 2021. When we publish new content we’ll make sure it meets accessibility standards.
- There are instances where focus highlighting is not present on some pages and fields within the service – users could lose focus on the page causing confusion. These instances fail WCAG 2.1 success criterion 2.4.7 (Focus Visible).
We plan to add focus highlighting to all pages and fields within the service by May 2021.When we publish new content we’ll make sure it meets accessibility standards.
- There are some instances of illogical heading structure making it difficult for screen reader users to determine layout and relationships between different sections of content. These instances fail WCAG 2.1 success criterion 2.4.10 (Section Heading).
We plan to make all headings throughout the site logical and sequential by May 2021.When we publish new content we’ll make sure it accessibility standards.
- There are some instances where it does not specify how to solve errors made whilst completing the form this could cause confusion for all users as they will be unsure of how to fix mistakes. These instances fail WCAG 2.1 success criterion 3.3.3 (Error Suggestion).
We plan to add text prompts and clear error messaging making sure we are compliant with GDS standards by May 2021.When we publish new content we’ll make sure all error messaging meets accessibility standards.
- Throughout the site prompt texts comes under the input fields, this will cause difficulty for screen reader users as they will not know in advance what is required for each of the input fields prior to entering. These instances fail WCAG 2.1 success criterion 3.3.5 (Help).
We plan to add text prompts above the input fields throughout the site making sure they are compliant with GDS standards by May 2021.When we publish new content we’ll make sure all prompt text is correctly placed meeting accessibility standards.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Please see information is provided in our Accessible documents policy
Live video
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
What we’re doing to improve accessibility
Driver and Vehicle Licensing Agency (DVLA) is working to improve the accessibility of all of its services. Our newer services will be updated to ensure compliance to Accessibility standards during 2020 to early 2021. Our older services are currently being reviewed with the aim to replace them with simpler more accessible services during the next two years.
Preparation of this accessibility statement
This statement was prepared on 1st March 2021. It was last reviewed on 1st March 2021.
This website was last tested on 21st April 2020. The test was carried out by the Digital Accessibility Centre Limited.
4 customer journeys were tested which encompassed happy and unhappy paths. This approach ensured we had a variety of user scenarios to test accessibility effectively.
Journey 1: an end to end successful retention, which included payment.
Journey 2: a system generated error induced journey at entering postcode details
Journey 3: a system generated error induced journey on entering keeper name
Journey 4: a user generated cancel transaction, where user cancels the transaction at payment stage
