This website is run by Ealing Council. We want as many people as possible to be able to use this website. 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:
- Some text areas do not have a description and means it may be difficult to screen reader users.
- Insufficient contrast between text and it’s background on some pages.
- Some webpage URLS can be identified by colour only.
- Some of our online forms are difficult to navigate using just a keyboard.
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@example.com
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
Ealing 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 non-compliances’, listed below.
Non-compliance with the accessibility regulations
- Some links are only identified by colour, which means some users may find it hard to distinguish. This fails WCAG 2. success criterion 1.4.1.We plan to make sure there are other visual indicators of links besides the colour, such as underline or bold by December 2020. When we publish new content, we’ll make sure our use of links meets accessibility standards.
- Some text/form input fields have no descriptions indicating its purpose. This fails WCAG 2.success criterion 1.31, 3.3.2, 4.1.2. We plan to add descriptions to text/input fields as a HTML label by December 2020. When we publish new content, we’ll make sure that all forms with input fields or text areas are labelled.
- The colour contrast is insufficient between text and the background on some pages. This may cause problems for users with low vision and colour blindness. This fails WCAG 2. Success criterion 1.4.3. We plan to make sure the contrast ratio is at least 4.5:1 for normal text and 3:1 for large text by December 2020. When we publish new content, we’ll make sure our use of links meets accessibility standards.
- Some areas of the website do not highlight when put into focus, so keyboard users may find it hard to use the site. This fails WCAG 2. Success criterion 2.4.7. We plan to make sure that interface elements that can receive keyboard focus are highlighted on focus by December 2020. When we publish new content, we’ll make sure keyboard users can view easily and it meets accessibility standards.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By December 2020, we plan to either fix these or replace them with accessible HTML pages.
Any new PDFs or Word documents we publish will meet accessibility standards.
This website was last tested in August 2020 by Ealing Council. We used automated software Siteimprove.