Technical accessibility statement

Hammersmith & Fulham 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-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Colour contrast

Links in blocks of text 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).

The colour of the text and the colour of the background in our banner advertisements and tables are not insufficient contrast to each other. This fails WCAG success criterion 1.4.3 (contrast - minimum).

We plan to fix these issues by September 2020.

On our search result pages, the blue used for links and background colours has low contrast with the other colours it's used with. This fails WCAG success criterion 1.4.3 (contrast - minimum).

Images, video and audio content

Many images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.

Interactive tools and transactions

Forms built on the H&F website don't display error messages next to form fields or at the top of the page. This means users will only be informed if they have missed out a form field if their browser notifies them. This does not meet WCAG 2.1 success criterion 3.3.1 (error identification) and 3.3.3 (error suggestion).

We are investigating when this issue can be resolved.

The form fields and social sign-in buttons on the Disqus comments widget on news pages don't receive focus. This means keyboard users may not know where on the page they are. This does not meet WCAG 2.1 success criterion 2.4.7 (focus visible). Keyboard users who wish to sign up to use Disqus will get trapped in a loop between the social sign-in buttons and on the question mark icon when tabbing to registration questions. This does not meet WCAG 2.1 success criterion 2.1.2 (no keyboard trap).

We plan to switch to another comment provider when the H&F website is upgraded in 2021.

The status message showing the number of search results return doesn’t have an aria ‘status’ role enabling the message to be read out by assistive technologies. This fails WCAG 2.1 success criterion 4.1.3 (status message).

Navigation and accessing information

There is no option to skip repeated content on our search result pages. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

The search field on our search result pages uses an accesskey attribute of 'q'. Accesskeys may conflict with user or assistive technology shortcut keys. 


On mobile devices, some pages don't show in a single column and text can be hidden off-screen. This means users need to scroll up and down and from left to right to read information. This does not meet WCAG 2.1 success criterion 1.4.10 (reflow).

We are working on fixing pages with this issue, however tables are out of scope for this success criterion as they do require users to scroll in both directions. We will continually review pages with tables and where possible, present the information in a different way.

On the search result pages, the filter options under Council service and content type still appear in the tab order when the accordions are closed. This fails WCAG 2.1 success criterion 2.4.3 (focus order).

The more/less button in the council service accordion on search result pages don’t receive focus. This issue fails WCAG 2.1 success criteria 2.4.7 (focus visible).

Text, links and tables

On some pages, the same link text is used for links going to different destinations meaning users might not know the difference if this is not explained. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context).

We plan to make links distinguishable by September 2020. When we publish new content we’ll make sure links are distinct and meet accessibility standards.

The alt text for the H&F logo in the header is not sufficient to act as the link text. The logo in the footer doesn’t have any alt text meaning an empty link is presented to screen reader users. This fails WCAG 2.1 success criteria 1.1.1 (non-text content) and 2.4.4 (link purpose – in context).

We plan to fix these issues by September 2020.

Website code

Elements used in our website code that should normally be used to structure content, have also been used to style content. For example, heading tags (H1, H2 and so forth) have been used with CSS classes to mark-up things such as our council logo and social media buttons in our navigation bar.

This means our pages have an illogical heading structure when viewed using a screen reader and other assistive technology. This does not meet WCAG 2.1 success criterion 1.3.1 (information and relationships).

We plan to fix this by September 2020.

Disproportionate burden

Not applicable.

Content that’s not within the scope of the accessibility regulations


Online maps and mapping services are exempt from the regulations if essential information is provided in an accessible digital manner for maps intended for navigational use.

Some maps that we use for navigational purposes don’t have a text alternative giving the address of the location shown on the map. This fails WCAG success criterion 1.1.1 (non-text content).

We plan to add addresses for these locations by October 2020.

We also plan to improve the results page of the ‘Where’s my nearest’ tool to make it clearer that the results presented are in order of how close they are to the address given.

PDFs and other documents

Many of our older PDFs and Word documents don’t meet accessibility standards - for example, they may not be marked up so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).

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.

We have created a register of PDFs and Word documents that are essential for service delivery and we plan to either fix these, unpublish them or replace them with accessible HTML pages.

The accessibility regulations do not 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 replace as many PDFs as possible with accessible HTML pages.

Any new PDFs or Word documents we publish will meet accessibility standards unless we determine that they represent a disproportionate burden within the meaning of the accessibility regulations. 

We will publish key information contained in these publications on a web page or link to alternative sources of information. We will offer information in an alternative format on demand.

Ultimately, we plan to provide an accessible HTML version of the information as the primary source.

Pre-recorded media

Most of our videos don't have accurate edited captions. This doesn’t meet WCAG 2.1 success criterion 1.2.2 (captions pre-recorded). None of them have audio descriptions. This doesn’t meet WCAG 2.1 success criterion 1.2.5 (audio description pre-recorded).

The regulations do not apply to pre-recorded videos published before 23 September 2020. However, while these videos are not subject to the legislation, we have carried out an audit of all our videos and have begun a process of updating captions on our recently published videos.

Any new videos we publish will have edited captions, subtitles or be audibly described.

How we tested this website

We use Siteimprove and Silktide, automated testing tools to help us monitor and fix usability and accessibility issues as they occur. The web team also manually review and update the site to maintain any parts that automated testing cannot cover.

The website was last audited by an external organisation on 8 January 2019. The audit was carried out by Shaw Trust Accessibility Services and included technical and manual testing. The sample of pages reviewed in the audit was selected using the following criteria:

  • pages common to many websites - for example, homepage and contact us
  • pages with variations in layout and functionality
  • most visited pages
  • selecting pages at random

You can read the full accessibility test report (pdf 3.31MB).

What we’re doing to improve accessibility

When we update our website, we will carefully monitor new content to ensure it meets accessibility standards.

We will work to improve the accessibility of documents published on the website.

We plan to carry out in-depth user testing in the future, including with users of assistive technology.

We have monitoring in place to review the accessibility of the site on an ongoing basis. We use this monitoring to identify and fix any new issues that arise.

We plan to provide an accessible HTML version of any new information as the primary source rather than using a PDF.

This statement was prepared on 23 September 2019. It was last updated on 22 September 2020.