East London low income residents' discount accessibility statement
How accessible this application process 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 of the non-text content do not have equivalent text alternatives. Uploaded documents each have an adjacent "X" button to remove it, with a hidden label for assistive devices of "Remove [filename] file". However these delete buttons also have an aria-describedby attribute referencing a text of "Uploaded file: [filename]" which is not needed. The aria-describedby attribute should be deleted from these delete buttons. This fails WCAG 2.2 success criterion 1.1.1 (non-text content). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Expandable content, headings and subheadings haven't all been programmed correctly. Each <button> element should be inside an <h2> element. Multiple pages have headings where the <span> element needs to be converted to an <h2> element or subheadings where the <span> element needs to be converted to an <h3> element. In the section headed by the vehicle registration number, the 4 data items about charging are shown in a single list, visually. But they are marked up as 4 separate <dl> lists, not one. The same happens with multiple <dl> lists in the expandable content revealed by the Charge Details button. The additional <dl> elements need to be removed, to leave just one <dl> list containing 4 pairs of <dt>/<dd> list items. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
The file upload function does not have the correct programmatic sequence. Each file upload area shows "Drag your file here" then a button "Or browse to your files". But the text passed programmatically to assistive technology starts with "Or browse to your files" first, because the "Drag your file here" is marked up using ::after. This markup needs to be replaced with a plain text paragraph element of <p>Drag your file here</p> placed before the button, so it is in correct sequence before the button. This fails WCAG 2.2 success criterion 1.3.2 (meaningful sequence). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Page titles have not been used according to specification. Multiple pages have the same page title as the previous one in the process. Each page should have a different title, to distinguish it from other pages and, in a sequential process, to identify which step in the process it is. Parts of this application follows a single-page application model (SPA), so there are no page reloads. It is therefore necessary to use JavaScript to update the contents of the <title> element when moving from page to page. This fails WCAG 2.2 success criterion 2.4.2 (page titled). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Links have not been used according to specification. There are multiple "Edit" links that point to different URLs, and the links do not have any programmatic context to distinguish them. The relevant purpose needs to be included in the link so these links should be relabelled as "Edit address" and "Edit vehicle". The "visually-hidden" CSS style (on the wider TfL estate) or "assistive-text" CSS style can also be used so that the content is not visible on screen. This fails WCAG 2.2 success criterion 2.4.4 (link purpose). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Error messages have not been used according to specification. If an invalid postcode is entered, a text error message is displayed and conveyed programmatically. The error message is associated with the input element so that it is read out automatically when the input has focus. No further action for this is required. However, the error message, "Something went wrong. Please check your details and try again." is sometimes displayed and this is not programmatically conveyed. An aria-alert should be used for this. If one or more of the required files has not been uploaded when the Continue button is operated, this page remains on screen but no error message is shown to say why. Sometimes the Continue button is active in this situation, other times it is disabled. Focus should be placed on the first file field that has not been completed, and a message displayed above the field saying "[the document type wanted] file(s) has not been uploaded" or similar. An aria-describedby attribute should be used to associate the error message with the input element, so that it is announced when it has focus. This fails WCAG 2.2 success criterion 3.3.1 (error identification). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Multiple complimentary roles are used without an accessible name to identify them. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value). We plan to make these components meet this criterion by the end of June 2025.
The following "autocomplete" attributes must be added to the following textbox: Postcode: autocomplete="postal-code". This fails WCAG 2.2 success criterion 1.3.5 (identity input purpose). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
On multiple pages the combination of foreground and background colours do not have sufficient contrast. This fails WCAG 2.2 success criterion 1.4.3 (colour contrast). We plan to make these components meet this criterion by the end of June 2025.
At 200% zoom, the instructions such as "Should be paid", shown for the list of 4 charging types, extend beyond the edge of the viewport. At 400% zoom, these instructions also extend beyond the edge of the viewport, when using the WCAG-specified window width for this test. Media queries should be used to reflow these data items so that no content extends beyond the righthand edge of the viewport on zoom. This fails WCAG 2.2 success criterion 1.4.4 (resize text) and WCAG 2.2 success criterion 1.4.10 (reflow). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Labels do not all correctly describe topics or purpose on the upload documents page. It has multiple instructions all with the same text of "Drag your file here", and multiple buttons all with the same label of "Or browse to your files". Each text and button label should be amended to identify which file(s) each one applies to. E.g. "Drag your file here (Photo ID)" and "Or browse your files (Photo ID)". This fails WCAG 2.2 success criterion 2.4.6 (headings and labels). We plan to make this page meet this criterion by the end of June 2025.
The error message, "Something went wrong. Please check your details and try again." is sometimes displayed. This appears to happen when the system has timed out of the process for security, so the message should be something like, "You have been timed out. Please start again". This fails WCAG 2.2 success criterion 3.3.3 (error suggestion). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
The user is warned to "Choose the correct country of registration. You risk getting a penalty if you pick the wrong one" but it is omitted from the Review page at the end of the process. To correct, the data entered in this field should be displayed along with the other data on the Review Application page, and restate there the warning about the penalty. This fails WCAG 2.2 success criterion 3.3.4 (error prevention). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Pages with status messages have not been used according to specification. When a process is slow and a rotating progress indicator is displayed to indicate that processing is ongoing, this condition must be notified programmatically using an ARIA live region. If the 'Find address' button is operated when no postcode has been entered, an error message is shown on screen, but it is not announced the first time it appears. Only subsequent operating of the button results in the alert are being heard. We need to check the alert is being correctly initialised. This fails WCAG 2.2 success criterion 4.1.3 (status messages). We plan to make all pages where this issue is present meet this criterion by the end of June 2025.
Feedback and contact information
Call 0343 222 1234 (call charges may apply)
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 20 January 2025.
This website was last tested on 11 January 2025. The test was carried out by Test Partners, a third-party accessibility specialist.