Generate an Accessibility Statement

This accessibility statement applies to https://book.taxicardbooking.com

This website is run by London Councils. We want as many people as possible to be able to use this website. AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

Parts of this website are not fully accessible for example:

• Some interactive elements i.e. menu items cannot be accessed with a keyboard
• The calendar and autocomplete components cannot be used with a keyboard or assistive technology
• Many pages have a missing visible focus indicator
• An option to skip over repetitive content is not available
• It’s not possible to dismiss content that appears on hover with a keyboard alone
• Some buttons have missing alternative text and labels
• Some labels are missing and not associated with form elements

How to request content in an accessible format

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

• customerservices@cityfleet.co.uk
• 020 7908 0271

We’ll consider your request and get back to you in 10 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: customerservices@cityfleet.co.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

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

Compliance status

This website is non-compliant compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The ‘non-compliances’ are listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

• Several buttons can’t be accessed via keyboard alone. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard)
• When new content is shown the focus does not move into that section. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order)
• An obvious focus indicator is missing on several interactive elements, making it difficult for sighted people to navigate around pages using a keyboard. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible)
• A skip link was not provided meaning it was more difficult for a sighted person using a keyboard to skip over repetitive areas of the page such as the main navigation. This fails WCAG 2.1 success criterion 2.4.1 (Bypass Blocks)
• An accessible label was missing from a button. This fails WCAG 2.1 success criterion 2.5.3 (Label in Name)
• Content that appears on hover cannot be dismissed without moving the mouse. This fails WCAG 2.1 success criterion 1.4.13 (Content on Hover or Focus)

• There is insufficient colour contrast making it difficult for users who have visual impairments to read and interact with content. This fails WCAG 2.1 success criterion 3.4.3 (Contrast)

• Some ARIA landmarks are missing. This fails WCAG 2.1 success criterion 1.3.1 (Information & Relationships)
• There are structural errors that can affect the way the page is read to assistive technologies such a stray tag. This fails WCAG 2.1 success criterion 4.1.1 (Parsing)
• Page titles are not unique and do not describe the purpose. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled)
• Some links with the same link phrase were not programmatically associated with its relevant content. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose)

• Some images do not have appropriate alternative text or are missing alternative text. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content)

• Autocomplete has not been assigned to any form fields, this means users are required to explicitly input data for each session. This fails WCAG 2.1 success criterion 4.1.3 (Identify Input Purpose)
• Some checkboxes have not been implemented correctly resulting in causing difficulty for keyboard and assistive technology users to interact with the content. This fails WCAG 2.1 success criterion 1.3.1 (Information & Relationships)
• Labels were missing and not associated on a number of form fields. This fails WCAG 2.1 success criterion 1.3.1 (Information & Relationships)
• Error messages were not announced automatically to users who rely on assistive technology. This fails WCAG 2.1 success criterion 1.3.1 (Information & Relationships)
• Important changes in content and error messages which occurs dynamically is not announced automatically to users. This fails WCAG 2.1 success criterion 4.1.3 (Status Change)

• Components which act as an accordion have not been marked up correctly for users who rely on assistive technology to interact with the content. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value)
• The date picker is completely inaccessible and cannot be interacted with a keyboard or assistive technology. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value)
• Tab panels have not been implemented where required. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value)
• The autocomplete is difficult to use for users who rely on assistive technology and screen readers. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value)

• Users are automatically timed out after inactivity and redirected back to the login page without warning or an option to extend their session. This fails WCAG 2.1 success criterion 2.2.1 (Timing Adjustable)

• The language of the document was not set. This fails WCAG 2.1 success criterion 3.1.1 (Language of Page)
• Images do not have text alternatives. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content)
• The document has not been assigned any tags. This fails WCAG 2.1 success criterion 1.3.1 (Info & Relationships)
• The tabbing order of the PDF has not been structured. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard)

What we’re doing to improve accessibility

We plan to address the A issues by December 2020 and the AA issues by March 2021

Preparation of this accessibility statement

This statement was prepared on 2nd September 2020. It was last reviewed on 10 November 2020.

This website was last tested on 2nd September 2020 by Nomensa who manually audited 5 pages (Welcome, Book, My Bookings, Track Vehicle) and 1 PDF (Complaints Policy) against all level A and AA success criteria from Web Content Accessibility Guidelines 2.1. The approach to deciding on which sample of pages to test was based on the Website Accessibility Conformance Evaluation Methodology (WCAG-EM).