Accessibility statement for H&F Hive

This accessibility statement applies to H&F Hive. There’s a separate accessibility statement for the main H&F website.

This website is run by Hammersmith & Fulham Council through our third party supplier, Spacehive.

We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • zoom in up to 200% 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:

  • some pages are not mobile responsive and require horizontal scrolling to see all the content
  • some links are not accessible by keyboard alone
  • the use of colour on most pages does not meet colour contrast requirements
  • images are missing or do not have descriptive alternative text
  • some elements are missing labels meaning their purpose cannot be described to assistive technology users
  • there is no way to skip repeated links and move to the main content.

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 cit@lbhf.gov.uk

Reporting accessibility problems with this service

We're always looking to improve the accessibility of H&F Hive.

If you find any problems that aren't listed on this page or think we're not meeting the requirements of the accessibility regulations, please use our report form to let us know.

Report an accessibility issue

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 is committed to making H&F Hive, 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 [insert one of the following: ‘the non-compliances’, ‘the exemptions’ or ‘the non-compliances and exemptions’] listed below.

This website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The [insert one of the following: ‘non-compliances’, ‘exemptions’ or ‘non-compliances and exemptions’] are listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Colour contrast

There are many colours used across the website that don’t have enough contrast when used with a white background or white text. This is not compliant with WCAG 2.1 guideline 1.4.3 (contrast - minimum).

In the accordions on the homepage, links are only differentiated from text by colour and need another distinguishing feature. This is not compliant with WCAG 2.1 guideline 1.4.1 (use of colour).

Images, video and audio content

Some images and icons across the website are missing alt tags or do not have descriptive alternative text that makes sense as the link text. This is not compliant with WCAG 2.1 guideline 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).

Interactive tools and transactions

Some elements are missing labels meaning their purpose cannot be described to assistive technology users.

This includes the:

  • filter options on the Projects page
  • search and ‘Get our newsletter’ input fields on individual project pages.

This is not compliant with WCAG 2.1 guidelines 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

Navigation and accessing information

There is no way to skip repeated links and move to the main content. This is not compliant with WCAG 2.1 guideline 2.4.1 (bypass blocks).

The social media share icons on the homepage have been included in a region however the aria-labelledby used to describe the region does not provide an accurate description. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

Landmarks and regions are used but not all content is included in one of these. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

The Impact page is missing a page title. This is not compliant with WCAG 2.1 guideline 2.4.2 (page titled).

Technology

The H&F hive pages are not mobile responsive and require horizontal scrolling to see all the content. This is not compliant with WCAG 2.1 guideline 2.4.10 (reflow). The individual projects pages do not have this problem.

There are some links on the site which are not accessible by keyboard alone, however screen reader users can access them in browse mode. These links do not appear in the tab order and don’t receive focus. This is not compliant with WCAG 2.1 guidelines 2.1.1 (keyboard), 2.4.3 (focus order) and 2.4.7 (visible focus).

On the individual project pages, the focus order does not follow a logical sequence (left to right), for example in the header navigation, and not all interactive elements are included such as the Like, Follow and Like this project buttons. This fails WCAG success criterion 2.1.1 (keyboard) and 2.4.3 (focus order).

When a user hovers or focuses on the ‘follow’ button, a tooltip appears. However, this content cannot be dismissed using a keyboard and disappears when the mouse point moves towards it. This is not compliant with WCAG 2.1 guidelines 1.4.13 (content on hover or focus).

The iFrame for Google maps on individual project pages is missing a title using the title attribute (title=””), that describes the content. This is not compliant with WCAG 2.1 guideline 4.1.2 (name, role, value).

Text, links and tables

Layout tables are used to present related elements however they should not be used in HTML5. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

There are several pages on the website where multiple H1 headings are used on the same page and heading levels are skipped. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

The small tag has been used to alter text size when this should be done with CSS. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

In the ‘Other information’ accordion on the homepage, the text has not been formatted correctly as looks like it should appear in a list. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

There are various instances of the H&F logo and other images being used as image links across the site, however they are missing alt tags, or don’t have descriptive alt text to be used as the link text. This is not compliant with WCAG 2.1 guidelines 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).

Some links on the site contain no text. This means the function or purpose of the link will not be presented to the user. This can introduce confusion for keyboard and screen reader users. This is not compliant with WCAG 2.1 guideline 2.4.4 (link purpose - in context).

On the Impacts page, the link text ‘LBHF website’ is used to go to different destinations multiple times. Link text should be distinguishable so users know they go to different places. This is not compliant with WCAG 2.1 guideline 2.4.4 (link purpose - in context).

On the news page, the panels link to anchor links on the page, but the destination does not exist as they open in a pop-up box. This is not compliant with WCAG 2.1 guideline 1.3.1 (info and relationships).

Website code

On some pages, the ID used for some elements on the page is not unique and is used elsewhere. This is not compliant with WCAG 2.1 guidelines 1.3.1 (info and relationships) and 4.1.1 (parsing).

When the CSS is disabled:

  • the controls for the Google Maps appear in different places on individual project pages
  • there are two Spacehive logos on individual project pages
  • there are duplicate headings and navigation links
  • the image gallery on individual project pages is duplicated
  • there is an empty iFrame at the bottom of the page.

There is also a section on ‘what are you offering’ that is not presented when CSS is turned on. These issues fail WCAG 2.1 success criterion 1.3.2 (meaningful sequence).

The form fields in the ‘what are you offering’ section are all missing labels and the radio button options are not grouped in a fieldset. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

Disproportionate burden

Not applicable.

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

Pre-recorded media

The videos on individual project pages do not include captions and some may require, but do not include audio description. This fails WCAG 2.1 success criterion 1.2.2 (captions - prerecorded), 1.2.3 (audio description or media alternative - prerecorded) and 1.2.5 (audio description - prerecorded). These videos are produced by the organisations seeking donations and within the meaning of the regulations are third party content that is exempt from the regulations. We will, however, guide these organisations on how to make accessible videos.

Maps

The maps used on H&F Hive are not intended for navigational use and are exempt from the regulations.

How we tested this service

This service was last tested on 17 September by Hammersmith & Fulham Council using:

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

What we’re doing to improve accessibility

We're working with the supplier, Spacehive, to fix the issues in this statement and to make the system more usable for all users.

Preparation of this accessibility statement

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