Your cookie settings

We and our partners use cookies and similar technologies to help you with your payments and journeys, remember your login, use webchat, understand how our website is used and show you content and adverts you might be interested in.

Some of our partners rely on legitimate interests to use your personal data, instead of your consent. You have the right to reject this. View our partners to find out more.

Find out more about our cookies and how to manage your settings. If this page is blocked by a cookie pop-up, choose ‘Accept only essential cookies’ to then see the page.

We use essential cookies to ensure our website works properly. Any other cookies will only be set if you select ‘Accept all cookies’ below or by clicking ‘Manage cookies’ to learn more.

Product Information Register accessibility statement

This accessibility statement applies to the Transport for London website https://tfl-productinformationregister.oncreate.app/
 

This website is run by Transport for London and built using the Liberty Create platform from NetCall.  

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. 

We know some parts of this website are not fully accessible. These issues are described below under the heading "Non-Accessible content". 

How accessible this website is 

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

Some PDF or Word documents may not be fully accessible. To request an accessible version please email TfLAccessibility@tfl.gov.uk. 

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: 

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, contact: smbproductinformationregister@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 websites 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 Web Content Accessibility Guidelines v2.2 

Some mandatory fields are marked only by an asterisk and have no alternative text. This fails WCAG criterion 1.1.1 (Non-text content). We plan include alternative text to affected pages by March 2026.  

Some navigation components are not identified by the correct landmark or are not formatted correctly. This means that people using screen readers or keyboard navigation may not be able to infer information, structure, and relationships between the interface elements. This fails WCAG criterion 1.3.1 (Info and Relationships). We plan to meet this criterion by March 2026. 

Some hover states and focus states of buttons rely on a change of background colour which has a contrast of 1:4:1 which is less than the 3:1 required. This may make states difficult to identify for people with visual impairments. This fails WCAG criterion 1.4.1 (Use of colour). We plan to meet this criterion by March 2026.  

Some navigation elements are not fully operable by keyboard. This means that on some pages users of keyboards may find it difficult to operate, specifically evidence submission and product searching. This fails WCAG criterion 2.1.1 (Keyboard navigation). We plan to meet this criterion by March 2026. 

There is one instance when using Firefox, you are unable to move beyond the "Country" dropdown list when using only a keyboard to navigate. This means that on some pages users of keyboards may be unable to make a produce a product assessment submission. This fails WCAG criterion 2.1.2 (No Keyboard Traps). We plan to keep monitoring the impact of this.  

Some page title elements have the same value as other pages. This means that some users with visual and cognitive disabilities will be unable to differentiate content. This fails WCAG criterion 2.4.2 (Page Titled). We plan to keep monitoring the impact of this. 

Some logo images and buttons do not describe the purpose of the control. This means that some users with motion impairment or cognitive limitation will be unable to skip links they are not interested in. This fails WCAG criterion 2.4.4 (Link Purpose - In Context). We plan to keep monitoring the impact of this. 

In some input fields, the accessible label name doesn't match the visible one. This fails WCAG criterion 2.5.3 (Label in Name). We plan to keep monitoring the impact of this. 

There are some instances where labels are not persistent when a user enters data in the field. This fails WCAG criterion 3.3.2 (Labels or instructions). We plan to meet this criterion by March 2026. 

There are various instances where a user interface components name and role can't be programmatically determined. This may mean that the function of a component, like a button or a link, is not clear. This fails WCAG criterion 4.1.2 (Name, role, value). We plan meet this criterion by March 2026. 

In some input fields, there is no correct autocomplete attribute. This fails WCAG criterion 1.3.5 (Identify Input Purpose). We plan to meet this criterion by March 2026. 

Some text only provides 3 combinations of colour which does not give a sufficient contrast. This may make the text difficult to read for users with a visual impairment. This fails WCAG criterion 1.4.3 (minimum contrast). We plan to keep monitoring the impact of this.  

There is one instance where application reports has some text box labels which are illegible as they overlap each other. This fails WCAG criterion 1.4.4 (Resize Text). We plan to keep monitoring the impact of this. 

There are some instances where content cannot be presented without loss of information or functionality at 400% zoom. This fails WCAG criterion 1.4.10 (Reflow). We plan to meet this criterion by March 2026. 

Some combinations of adjacent colour in components do not have a contrast ratio of at least 3:1. This means that some active user interface components (i.e., controls) and meaningful graphics are not distinguishable by people with moderately low vision. This fails WCAG criterion 1.4.11 (Non-text Contrast). We plan to meet this criterion by March 2026. 

There are many instances of where headings as labels do not describe a topic or a purpose. This means some users using screen-readers will struggle to interpret certain pages. This fails WCAG criterion 2.4.6 (Headings and Labels). We plan to meet this criterion by March 2026. 

There are some instances of buttons which do not display a focus indicator when using Firefox as a browser. This fails WCAG criterion 2.4.7 (Focus Visible). We plan to keep monitoring the impact of this. 

Some status messages can't be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. This means that users are unaware of changes in content that are not given focus to. This fails WCAG criterion 4.1.3 (Status messages). We plan to meet this criterion by March 2026. 

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

PDFs and other evidence documents 

Some of our PDFs and Word documents are evidence submissions from external suppliers, which are outside of the scope of accessibility requirements.  

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 and created by Transport for London. To request an accessible version of any of these PDFs, please email TfLAccessibility@tfl.gov.uk. 

We intend that any new PDFs or Word documents TfL publishes will meet accessibility standards. 

Preparation of this accessibility statement 

This statement was prepared on 18 November 2024. It was last reviewed on 9 May 2025. 

This website was last tested on 1 November 2024. The test was carried out by Test Partners, a third-party accessibility specialist. 

We used this approach to decide on a sample of pages to test: 

We tested the 18 pages which had the highest usage. In addition to this we tested at least one instance of each different page template used throughout the site. The total number of pages tested was 18. 

Version 1.1 

5 May 2025