This website is run by 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 400% 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. You can see a full list of any issues we currently know about in the Non-accessible content section of this statement.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, email the H&F web team at webmaster@lbhf.gov.uk
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 contact@fosterwithwestlondon.org.uk
We’ll consider your request and get back to you in 10 working days.
Enforcement procedure
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
Hammersmith & Fulham Council is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to ‘the non-compliances’ listed below.
Non-accessible content
Non-compliance with the accessibility regulations
Events
Most events listed on this website are recurring and have the same name. The event name is used as the link text on the events listing page and does not provide context to assistive technology users as to which date that event falls on. This fails WCAG success criteria 2.4.4 (Link purpose - in context).
Cookiebot
We use Cookiebot as our cookie consent tool on this website, however, it has several accessibility issues.
The icon (button) to open the cookiebot widget has generic labels for assistive technology users: 'Open widget' and 'Close widget'. This fails WCAG success criterion 2.4.4 (Link purpose - in context)
Links to third-party websites have different visible labels and accessible names, meaning people who use voice commands can't activate the links. This fails WCAG 2.2 success criterion 2.5.3 (Label in name).
Links to third-party websites also have tooltips that appear when the pointer hovers over them. However, the tooltips disappear when the pointer moves away from the link. This fails WCAG success criterion 1.4.3 (Content on hover or focus).
Keyboard users can only exit the Cookiebot widget by selecting the X (Close widget or close banner) button. Selecting Allow all, Allow section or Deny minimises the widget, but the focus stays within it. This fails WCAG success criteria 2.1.2 (No keyboard trap) and 2.4.11 (Focus not obscured - minimum).
At 300% zoom and higher, the Allow selection and Deny buttons do not receive focus, meaning users can only select Allow all. This fails WCAG success criterion 2.1.1 (Keyboard).
At 300% zoom and higher, the following elements do not have a visible focus:
- the close widget and close banner buttons
- the preferences, statistics and marketing checkboxes
This fails WCAG success criterion 2.4.7 (Focus visible).
Cookiebot is aware that their product does not meet accessibility standards but don't have a timeline for resolving these issues. We are looking at alternative cookie consent tools that are accessible and allow us to fully comply with privacy regulations.
Disproportionate burden
Not applicable.
Content that’s not within the scope of the accessibility regulations
Not applicable.
Preparation of this accessibility statement
This statement was prepared on 31 March 2025. It was last reviewed on 3 April 2025.
This website was last tested on 28 March 2025. The test was carried out by Hammersmith & Fulham Council.