This website is run by the Defend Councils Home Unit and Hammersmith & Fulham Council. We want as many people as possible to be able to use this website.
For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
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:
- there is no way to skip repeated links and move to the main content
- images are missing or do not have descriptive alternative text
- accordions can't be opened by keyboards
- some pages have illogical heading structures
- there isn't a focus style for most interactive elements
- assistive technology users will have difficulty locating the search.
- The homepage is missing a top-level heading
- Some pages have an illogical heading structure as H2 and H3 headings have been skipped
- Multiple H1 headings are used on the search results page
- Duplicate headings are used on the Who are we page.
- An empty iframe with no title and offers no functionality is displayed at the bottom of every page
- A text area related to the CAPTCHA is displayed and has no label
- The map on the Contact page covers most content meaning it can’t be read.
- Accessibility insights for web
- Browser inspection tools
- Manual testing
- Text spacing
- Web developer.
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille email us at firstname.lastname@example.org
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 us at 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
The Defend Councils Home Unit and Hammersmith & Fulham Council are committed to making this 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 and exemptions listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
On all pages there isn't sufficient contrast between the colour of the text and the background, making it hard to read the information. This doesn’t meet WCAG 2.1 success criterion 1.4.3 (contrast - minimum).
Form fields also do not meet minimum colour contrast requirements. This fails WCAG 2.1 success criterion 1.4.11 (non-text contrast).
Some links are only identifiable by colour and don’t meet the minimum colour contrast ratio needed between links and surrounding text. This fails WCAG 2.1 success criterion 1.4.1 (use of colour).
Images, video and audio content
Some images are missing an alt attribute and alternative text. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
Interactive tools and transactions
The link text for the search link has been hidden in a way that means assistive technologies will present the web address for the site. This fails WCAG 2.1 success criterion 2.4.4 (link purpose – in context).
Although the search works, it has been included in a form tag which means it should have a submit button to maximise predictability. This fails WCAG 2.1 success criterion 3.2.2 (on input) and 4.1.2 (name, role, value).
Autocomplete tokens have not been added to relevant form fields. This fails WCAG 2.1 success criterion 1.3.5 (identify input purpose). Modern browsers such as Chrome will still offer users autocomplete options on appropriate fields.
The error summary message is position after the Send button and may be missed by some users. This fails WCAG 2.1 success criterion 3.3.1 (error identification).
The ‘contact’ and ‘join our mailing list’ forms are missing the aria-atomic attribute. This ensures assistive technologies can read error messages after more than one invalid submission has been made. This fails WCAG 2.1 success criterion 3.3.1 (error identification).
No suggestions are given on how to correct invalid entries made on forms. This fails WCAG 2.1 success criterion 3.3.3 (error suggestion).
Navigation and accessing information
There is no skip to main content link available. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
The accordions on the Question and Answer page are not accessible to keyboard users. This fails WCAG 2.1 success criterion 2.1.1 (keyboard).
Most interactive elements do not have a focus style meaning keyboard users may not be able to identify where they are on the page. This fails WCAG 2.1 success criterion 2.4.7 (focus visible). Modern browsers should provide a focus ring to show users which element is highlighted, but we will work on providing one.
Text, links and tables
There are several issues to do with headings:
These issues fail WCAG 2.1 success criterion 1.3.1 (info and relationships) and the last issue also fails 2.4.6 (headings and labels).
On some pages, the same link text is used to go to different destinations multiple times. The link text is also too generic meaning that it’s purpose can not be identified when read out of context. These issues fail WCAG 2.1 success criterion 2.4.4 (link purpose – in context).
The search fields on the Search Results page both have the same ID meaning they have multiple labels and neither are read out by screen readers. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 4.1.1 (parsing).
When the CSS is disabled:
These fails WCAG 2.1 success criterion 1.3.2 (meaningful sequence).
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Our PDFs may not be fully accessible to all users. For example, they may not be structured to be accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2. The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
However we plan to turn this document into an HTML web page.
The videos on this website include captions but do not have audio descriptions for all text that is presented on screen or scenes with no dialogue. This fails WCAG 2.1 success criterion 1.2.3 (audio description or media alternative - prerecorded) and 1.2.5 (audio description - prerecorded). We may not add audio description to these videos because prerecorded video published before 23 September 2020 is exempt from meeting the accessibility regulations.
Any prerecorded video content we publish after 23 September 2020 will meet accessibility standards.
We display a map on the Contact page to show where Hammersmith & Fulham is. Because the map is not intended for navigational use it is exempt from the regulations.
Our website contains third party content. For example, we link to a PDF created by the Greater London Authority (GLA). We do not have control over and are not responsible for the accessibility of this content, but we endeavour to work with third parties to improve its accessibility.
How we tested this service
This service was last tested on 21 September 2020 by Hammersmith & Fulham Council using:
What we’re doing to improve accessibility
We're working to fix the issues in this statement and to make the website more usable for all users.
Preparation of this accessibility statement
This statement was prepared on 23 September 2020. It was last reviewed on 23 September 2020.