This accessibility statement applies to https://www.londoncouncils.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
We know some parts of the London Councils website aren’t fully accessible:
- some buttons and links can’t not be triggered using a keyboard
- many of our PDFs don't meet accessibility standards and are not accessible to a screen reader
- many pages have hidden content which is keyboard focusable
- some buttons don’t have a visible focus indicator
- some pages have insufficient colour contrast
- some images are missing alternative text
- some buttons do not have appropriate labels
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:
- Email: [email protected]
- Phone: 020 7934 9759
- Postal address: 59½ Southwark Street, London SE1 0AL
We try to respond as soon as we can, generally within ten 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: [email protected]
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 Council 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
- A number of accordions and links could not be accessed with a keyboard alone, this makes it difficult for users who rely on keyboard navigation. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard)
- All navigation items which are hidden still receives focus whilst navigating with a screen reader and keyboard. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard)
- A visible focus indicator is missing on some buttons, making it difficult for people who rely on keyboard navigation to see where they currently are on the page. This fails WCAG 2.1 success criterion 2.4.7 (Keyboard)
- A skip link had been implemented incorrectly as it’s not obvious to visual users that an option to skip repetitive content has been provided. This fails WCAG 2.1 success criterion 2.4.1 (Bypass Blocks)
- 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)
- Some images and infographics do not have appropriate alternative text or are missing alternative text which results in the file path being announced to users who rely on screen readers. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content)
- Some buttons are missing labels. 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 end tags and nesting issues. This fails WCAG 2.1 success criterion 4.1.1 (Parsing)
- Custom components such as accordions have not been marked up correctly for people who rely on assistive technology to interact with the content. This fails WCAG 2.1 success criterion 4.1.2 (Name, role, value)
- 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)
- Loss of information occurs when a user overrides the current text spacing. This fails WCAG 2.1 success criterion 1.4.12 (Text Spacing)
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 11 September 2020.
This website was last tested on 2 September 2020 by Nomensa who manually audited 6 pages (Homepage, Eligibility, Press Releases, Search, Why work for us? And Podcast) 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).