Santander Cycles website accessibility statement

This accessibility statement applies to the Transport for London website www.tfl.gov.uk/modes/cycling/santander-cycles

This website is run by Transport for London. 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.

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

Some decorative elements are exposed to screen reader software. This makes the experience more verbose, but does not prevent people from conducting any tasks. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to make all focusable components meet this criterion by July 2024.

Headings have not been used according to specification. Some text components should be in heading elements and are not. 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 focusable components meet this criterion by July 2024.

The Login, Recover password and Sign up pages do not use landmark elements to convey document structure. 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 focusable components meet this criterion by July 2024.

On the Notification Preferences page, some input elements are missing explicitly associated text label elements. This may make it harder for screen reader software users to understand what to enter into those input elements. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships). We plan to make all focusable components meet this criterion by July 2024.

The burger button to open and close the navigation is not keyboard operable. 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 focusable components meet this criterion by July 2024.

If the Update postal address pop-up window is opened, it is not possible to close the pop-up using just the keyboard. This fails WCAG 2.1 success criterion 2.1.2 (no keyboard trap). We plan to make all focusable components meet this criterion by July 2024.

There is no mechanism to bypass the main navigation. For keyboard users, that means there is no way to quickly reach the main content on a page. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks). We plan to make all focusable components meet this criterion by July 2024.

Some pages do not have page titles that describe the topic or purpose of the page. Screen reader software users will have to navigate to the main heading on the page to confirm that they are on the page they wanted when following a link. This fails WCAG 2.1 success criterion 2.4.2 (page titled). We plan to make all focusable components meet this criterion by July 2024.

When a form is submitted that contains errors, focus remains on the submit button rather than being sent to a general error message at the top of the page, or the first input element with a problem. 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 2.4.3 (focus order). We plan to make all focusable components meet this criterion by July 2024.

When a form is submitted that contains errors, error messages are provided in text, but these are not associated with the input elements and are not read out automatically by screen reader software. 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 make all focusable components meet this criterion by July 2024.

Some forms need instructions to be added, or the purpose of some components to be explained. This may make it harder for some users to complete forms. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions). We plan to make all focusable components meet this criterion by July 2024.

Several HTML5 validation errors that could have an impact on the accessibility of the page. This fails WCAG 2.1 success criterion 4.1.1 (parsing). We plan to make all focusable components meet this criterion by July 2024.

A small number of buttons and input elements do not have accessible names, so it is difficult for screen reader software users to know their purpose. The state (open or closed) of the menu is not conveyed to screen reader software users. This fails WCAG 2.1 success criterion 4.1.2 (name, role, value). We plan to make all focusable components meet this criterion by July 2024.

Input elements that capture personal information (e.g. first name) do not have appropriate 'autocomplete' attributes. This can make forms harder to complete for some people. This fails WCAG 2.1 success criterion 1.3.5 (identify input purpose). We plan to make all focusable components meet this criterion by July 2024.

Some content within pages do not provide sufficient colour contrast, making it hard for people with low vision to read or interact with controls. This fails WCAG 2.1 success criterion 1.4.3 (contrast (minimum)) and 1.4.11 (non-text contrast). We plan to make all focusable components meet this criterion by July 2024.

When using keyboard navigation, it can be difficult to see when focus is on the logout button on some browsers because there is no indication when the control has focus. This fails WCAG 2.1 success criterion 2.4.7 (focus visible). We plan to make all focusable components meet this criterion by July 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 11 August 2022. It was last reviewed in January 2024.

This website was last tested on 3 August 2022. 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 30 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 59.