Scrappage scheme website accessibility statement

This accessibility statement applies to the scrappage scheme application process.

How accessible this application process is

We know some parts of this website are not fully accessible.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, because of the non-compliances and exemptions listed below.

Non-compliance with the accessibility regulations

Headings have not been used according to specification. The heading "London road user charging" should be in a different heading element. This could have an impact on screen reader software users and how they understand the structure of pages and how they navigate within a page. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships). We plan to make all pages where this issue is present meet this criterion by the end of October 2024.

The file upload function does not conform to GOV.UK design standards. The file upload input needs to be clear and not hidden. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships). We plan to make the file upload controls meet this criterion by the end of October 2024.

You cannot manually enter a date into the date field and the date selector is not operable using just the keyboard. This may make it difficult for some users to easily navigate to all the pages in the website. This fails WCAG 2.1 success criterion 2.1.1 (keyboard navigation). We plan to make all date input elements meet this criterion by the end of October 2024.

On the Terms and Conditions page, if the continue button is pressed without selecting the checkbox, focus is sent to the start of the page. You must click into page otherwise focus is lost and cannot be regained. This fails WCAG 2.1 success criterion 2.1.2 (no keyboard trap). We plan to fix the checkbox on the Terms and Conditions page to meet this criterion by the end of October 2024.

A field in error should have the 'aria-invalid' attribute. This fails WCAG 2.1 success criterion 3.3.1 (error identification) and 4.1.3 (status messages). We plan to make all input elements handle errors this way by the end of October 2024.

Text instructions need to be added to some pages before the start of a form. Without instructions, some users may find it harder to complete forms successfully. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions). We plan to provide instructions for all forms and meet this criterion by the end of October 2024.

On pages with a date picker, the W3C nu html validator reports some html validation errors that may have an impact on the accessibility of the page. There are a small number of duplicate 'id' attributes relating to these components. These fail WCAG 2.1 success criterion 4.1.1 (parsing). We plan to fix all fix all relevant validation errors to meet this criterion by the end of October 2024.

The privacy notice expand and collapse component has the aria-expanded on the <div>, when it should be on the <button>. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value). We plan to make these components meet this criterion by the end of October 2024.

Multiple complimentary roles are used without an accessible name to identify them. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value). We plan to make these components meet this criterion by the end of October 2024.

There is no general error message at the top of the page for when no documents are successfully uploaded. This may make it hard for screen reader software users to realise there is a problem, and to fix it. This fails WCAG 2.1 success criterion 3.3.1 (error identification) and 4.1.3 (status messages). We plan to fix this issue by the end of October 2024.

Feedback and contact information

We'll consider your request and aim to get back to you within 10 working days.

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, email: TfLAccessibility@tfl.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

Transport for London is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Preparation of this accessibility statement

This statement was prepared on 30 January 2023.

This website was last tested on 30 January 2023. The test was carried out by Test Partners, a third-party accessibility specialist.