Accessibility statement for LBHF libraries and archive blog

This blog is run by H&F Libraries and Archives.

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
  • 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:

  • the site can’t be zoomed without text spilling off the screen
  • blog posts are missing H1 headings
  • the colour contrast between grey links and backgrounds are not sufficient enough
  • some image links are missing alternative text
  • there isn’t an option to skip repeated link.

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, please get in touch by emailing us at

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website.

If you find any problems that aren’t listed on this page or think we’re not meeting the requirements of the accessibility regulations, email us at

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 Libraries and Archives 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

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions.

Non-accessible content

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

Non-compliance with the accessibility regulations

Colour contrast

There is not enough contrast between the grey text and backgrounds it’s used on. This fails WCAG 2.1 success criterion 1.4.3 (contrast – minimum).

Images, video and audio content

Some images used as links don’t have alternative text meaning empty links are presented to assistive technologies. This fails WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose – in context).

Interactive tools and transactions

The categories dropdown list is contained in a form element but doesn’t have a submit button. This fails WCAG 2.1 success criterion 3.2.2 (on input).

The field where users can enter their email address to receive notifications of new blog posts does not have a label. This is also the case for the leave a comment text area on blog posts. Both these issues fail WCAG 2.1 success criterion 1.3.1 (info and relationships), 3.3.2 (labels and instructions).

Navigation and accessing information

An option to skip repeated links is present but does not work. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).


When using the tab key to jump between elements, the focus ring disappears in between the publish date link and first link in the blog post. This is because the text and link showing the author of the blog has been hidden from view but not the tab order. This fails WCAG 2.1 success criterion 2.4.7 (focus visible).

The social login options for leaving comments can only receive focus when you tab back from the email address field, however the Google icons still does not receive focus when you do this. This fails WCAG 2.1 success criterion 2.1.1 (keyboard) and 2.4.3 (focus order) and 2.4.7 (focus visible).

Text, links and tables

Blog posts are missing H1 headings. This fails WCAG 2.1 success criteria 1.3.1 (info and relationships).

The headings for widgets and filter options are all marked up as H3 headings when they should be H2. This fails WCAG 2.1 success criteria 1.3.1 (info and relationships).

The tables used on the rooms for hire page don’t have summaries or header cells. This fails WCAG 2.1 success criteria 1.3.1 (info and relationships).

Because the homepage displays all the blog posts, the share this and comment links are repeated after each blog meaning the same link text is used to go to different destinations. This fails WCAG 2.1 success criteria 2.4.4 (link purpose – in context).

Disproportionate burden

Not applicable.

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

Third-party content

Our website contains third-party content such as Twitter feeds and commercial advertisements. We do not have control over and are not responsible for the accessibility of this content. However, we have assessed their compliance.

For example, in the LBHF libraries twitter feed:

  • the emojis in tweets are missing alternative text
  • Links in tweets are only distinguished from normal text using colour
  • Some tweets have the same link text that go to different destinations.

On the commercial advertisements, there is not enough contrast between the report this ad links and the backgrounds it’s used on.

How we tested this service

This website was last tested on 24 August 2020 by Hammersmith & Fulham Council using:

  • Accessibility insights for web
  • Browser inspection tools
  • Manual checking
  • NVDA
  • Siteimprove
  • Text spacing
  • WAVE
  • Web developer.

What we’re doing to improve accessibility

We’re investigating more modern WordPress themes to use for the blog and are making plans on how to fix content specific issues.

Preparation of this accessibility statement

This statement was prepared on 23 September 2020. It was last reviewed on 23 September 2020.