School Party Travel Scheme microsite accessibility statement

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. See below.

Compliance status

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

Non-compliance with the accessibility regulations

Information, structure, and relationships are not fully specified correctly. The remaining incorrect specifications include the Footer container; various features around Applications which would affect screen readers; and Re-send application link. For managing Schools, Rules, and Reference Data, there is no indication for screen reader users as to the currently selected item in list. This fails WCAG 2.1 success criterion 1.3.1 (information and relationships). We plan to make all information and relationship components meet this criterion by February 2023.

Some pages have the same page titles as others when they should be more specific, including Create application, Manage school, Manage rules, and Manage reference data. Manage places does not have an appropriate title. 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 page title components meet this criterion by February 2023.

In some tables it is not conveyed to the screen reader software which column the data is sorted by. Pages affected include Applications awaiting decision, Ticket times, Search applications, and Manage reference data - place names. This fails WCAG 2.1 success criterion 2.4.4 (link purpose). We plan to make all sorted table components meet this criterion by February 2023.

Some of the error messages provided in text 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. Pages affected include Create application (pages 1 and 2) and Re-send application link. This fails WCAG 2.1 success criterion 3.3.1 (error identification). We plan to make all error components meet this criterion by February 2023.

On every page there is at least one aspect that does not provide sufficient colour contrast, making it hard for people with low vision to read or interact with controls. On seven pages there are two aspects and on three pages there are three aspects not providing sufficient colour contrast. This fails WCAG 2.1 success criterion 1.4.3 (contrast (minimum)). We plan to make all text meet this criterion by February 2023.

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 February 2023.

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

Avoid using the drag and drop component if you're filling in a form on our Help & contacts page and need to supply supporting documents to help us answer your enquiry, like a PDF file or image. Alternatively, email any supporting documents to TfLAccessibility@tfl.gov.uk along with your full name so we can match them with your form submission.

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: 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.

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

PDFs and other documents

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. 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 we publish will meet accessibility standards.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Preparation of this accessibility statement

This statement was prepared on 7 December 2022. 

This website was last tested on 11-12 November 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. The total number of pages tested was 20.