Do Something Good is committed to providing a website that is accessible to the widest possible audience, regardless of technology and ability.
We are working to make this website more convenient and easy to use, by implementing many of the available guidelines and standards.
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.
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.
Some images are missing a text alternative
On some pages, the same link text is used to go to multiple destinations
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.
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: firstname.lastname@example.org
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).
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.
Some links are only identified by colour, so people 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.
On some pages the link text used goes to multiple different destinations. This fails WCAG 2. Success criterion 2.4.4. We plan to make sure links are distinguishable and clear that they lead to different destinations by December 2020. When we publish new content, we’ll make sure that are links meet accessibility standards.
Image links are missing alternative text. This fails WCAG 2. Success criterion 2.4.4. We plan to make sure are image links have supporting text stating the purpose of the link by December 2020. When we publish new content, we’ll make sure that are image links meet 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 are text areas are labelled.
The colour contrast is insufficient between text and the background on some pages, so 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 of the elements of our web forms are not connected or named with a description. This fails WCAG 2. Success criterion 1.3.1. We plan to make sure that our web form elements check boxes and/or radio buttons are grouped and named by December 2020. When we publish new content, we’ll make sure our use of web forms meets accessibility standards.
Some of our web form labels are not connected to a form control to help render content properly to the user. This fails WCAG. 2 Success criterion 1.3.1. We plan to make sure that our web form labels are connected to a web form control by December 2020. When we publish new content, we’ll make sure our web forms meet 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.
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 statement was prepared on 15 September 2020. It was last reviewed on [28 September 2020].
We are continuously seeking out solutions to improve the accessibility of this site, if you should experience ay difficulty in using this site which you believe could be addressed by us, please contact us at: email@example.com.