This accessibility statement applies to https://www.londontribunals.gov.uk/
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 pages have poor colour contrast
- Some pages don’t have a logical heading structure
- Some hidden content can be still accessed
- Error messages disappear after 5 seconds
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:
020 7520 7200
We’ll consider your request and get back to you in 10 working days 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:
020 7520 7200
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.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the following ‘non-compliances’ listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Hidden buttons that are in the background receives focus. This fails WCAG 2.1 success criterion 2.4.3 (Focus Order)
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) and 1.4.11 (Non-Text Contrast)
Colour alone has been used to convey meaning. This fails WCAG 2.1 success criterion 1.4.1 (Use of Colour)
Error messages temporarily appears and then disappears after 5 seconds. This fails WCAG 2.1 success criterion 1.3.1 (Information & Relationships)
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 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)
A progress bar uses visual cues to indicate where the user is within a journey, however the same information is not provided to users who rely on screen readers i.e. completed, current and to-do steps. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value)
What we’re doing to improve accessibility
We plan to fix these issues by October 2020.
Preparation of this accessibility statement
This statement was prepared on 2 September 2020. It was last reviewed on 07 September 2020.
This website was last tested on 2 September 2020 by Nomensa who manually audited 5 pages (Homepage, Key Cases, Evidence Article, Plan & Prep, Feedback Form) 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).