TfL Go accessibility statement

This accessibility statement applies to the TfL Go app, available on iOS and Android.

TfL Go is run by Transport for London. We want as many people as possible to be able to use the app. For example, that means you should be able to:

  • Change colours and contrast levels
  • Resize text by activating dynamic type in iOS and large fonts, screen zoom in Android
  • Navigate most of the app using just a keyboard
  • Navigate most of the app using voice control in iOS and voice access in Android
  • Listen to most of the app using VoiceOver in iOS, Talk Back in Android

We have designed the layout of the app and the content within to be as simple as possible to understand. AbilityNet has advice on making your device easier to use if you have a disability.

How accessible the app is

We know some parts of TfL Go across iOS and Android are not fully accessible:

iOS

  • Some text has colour contrast issues
  • Some text cannot be resized

Android

  • Some text has colour contrast issues
  • Some text cannot be resized
  • Some buttons do not have the appropriate label

Reporting accessibility problems with TfL Go

We're always looking to improve the accessibility of the TfL Go apps. If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact: 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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about app accessibility

Transport for London is committed to making its apps 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, because of 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 

Some text does not have a contrast ratio of 4:5:1. 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 make all text meet this criterion by April 2023.

Some user interface components do not have a contrast ratio of at least 3:1 against adjacent colour. This may make the text difficult to read for users with a visual impairment. This fails WCAG criterion 1.4.11 (Non-text contrast). Focus state properties are determined by the operating system, which means that in cases where colour contrast requirements are not met this cannot be remedied by app developers.

Some text does not adjust with changes to accessibility text size. This may make the text difficult to read for users with a visual impairment. This fails WCAG criterion 1.4.4 (resize text). We plan to make all text meet this criterion by September 2023.

Some focusable components don't receive focus in an order that preserves meaning and operability. This may cause screen readers to announce some things in an order that might not be the most logical. This fails WCAG 2.1 success criterion 2.4.3 (focus order). We plan to continue to monitor this and resolve those issues as they arise.

Some components don't have correct labelling. This may mean that the function of a component, like a button or a link, is not clear. This fails WCAG 2.1 success criterion 2.4.3 (name, role, value). We plan to continue to monitor this and resolve those issues as they arise.

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

All stations on the standard and step-free tube map do not receive focus, because of the complexity of navigating the map solely using a screen reader or a wireless keyboard. In order to select a station, users can use the search functionality available in the same view.

Preparation of this accessibility statement

This statement was prepared on 13 June 2021. It was last reviewed on 19 August 2022. This website was last tested in January 2022. The test was carried out by Test Partners, a third-party accessibility specialist.

We tested all of the functionality of the app, including at least one instance of each station and stop template used in the app. The total number of pages tested was 17.