Accessibility statement

Using this website

This accessibility statement applies to lbhf.gov.uk

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 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)

You should also be able to select a language to get a page translated using Google’s translation service. This is a machine-based translation service, so we can't guarantee the accuracy or the sense of any given translation.

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.

Find out how to:

  • make your mouse easier to use
  • use your keyboard instead of a mouse
  • talk to your device
  • make your device talk to you
  • make text larger
  • change your colours
  • magnify the screen

Service applications

Most of our online services are provided by third-party applications - these are platforms and websites developed by external suppliers. Because the development of these third-party applications is partly or wholly out of our control, they may not conform to the same levels of accessibility as our main website.

Third-party applications include:

  • My Account
  • Online payments
  • FIS directory and SEND Local Offer
  • Public Access applications search (planning, building control and licensing)

We monitor the accessibility of these sites and ask suppliers to fix accessibility issues that arise. View the accessibility statements for our third-party systems.

We require that any new third-party systems we commission are Web Content Accessibility Guidelines 2.1 AA compliant.

How accessible this website is

We know some parts of this website aren’t fully accessible:

  • most PDFs aren't fully accessible to screen reader software
  • error messages only display temporary on forms and are generic
  • the colour contrast between links and the background are insufficient on our search result pages

Feedback and contact information

If you need information on this website in a different format like an accessible PDF, large print, easy read, audio recording or braille, please get in touch by emailing us at webmaster@lbhf.gov.uk

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, 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).

Contacting us by phone or visiting us in person

We provide a text relay service for people who are Deaf, hearing impaired or have a speech impediment. Please call 18001 followed by 020 8748 3020.

Alternatively, you can use Relay UK service. Relay UK (previously Next Generation Text) - helps people with hearing and speech difficulties communicate with anyone over the phone, using the national relay service.

Our customer service centre is wheelchair accessible and has a portable hearing loop.

Find out how to contact us.

Technical information about this website’s accessibility

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.

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 listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Documents

Many of our documents are not accessible in a number of ways including missing:

  • text alternatives for images
  • document structure properties such as headings and bookmarks
  • interactive controls for forms
  • a default document language
  • titles or have non-descriptive titles

We are working on making documents published since 23 September 2018 and older documents essential for service delivery, accessible and aim to complete this by April 2021. Examples of essential documents include PDFs with information on how users can access our services and forms published as PDF or Word documents.

We also publish documents that are not designed for reading online, for example, posters, leaflets or digital image files. These documents may not be accessible. We will identify them as printable documents and offer users an alternative format if requested.

Read more about what we are doing to improve the accessibility of documents.

Forms

Forms hosted on the H&F website such as the apply for a parking suspension form have some accessibility issues.

Form fields do not have autocomplete attributes which enable browsers to help users fill in forms with known information such as names, addresses and contact details. This fails WCAG 2.1 success criterion 1.3.5 (identify input purpose). We are adding autocomplete attributes to our forms but users can get around this if they use a browser that has an autofill feature.

Hidden grouping labels generated for radio buttons and checkbox items point to invalid IDs. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

Error messages are:

  • temporarily displayed and only appear one at a time
  • generic and do not give suggestions on how to correct the error

This does not meet WCAG 2.1 success criterion 3.3.1 (error identification) and 3.3.3 (error suggestion).

These outstanding issues will be resolved when we launch the first phase of our new website in early summer 2021. In the meantime, we have alternative ways for users to access the services provided through these forms via email or telephone.

Search result pages

Our search result pages have several accessibility issues. We're working with our supplier to resolve these issues and aim to complete this by April 2021.

Accesskeys

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

Colour contrast

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).

Headings

The search result pages have multiple H1 headings. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

Images

The alt text for the H&F logo in the header is not sufficient to act as 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).

Keyboard navigation

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).

Links

The URL links in the list of search results create additional navigation and repetition for keyboard and screen reader users.

Lists

The mark-up code for lists contains elements that should not be used. This fails WCAG 2.1 success criterion 4.1.1 (parsing).

Page titles

The results pages all have the same page title. This fails WCAG 2.1 success criterion 2.4.2 (page titled).

Search field

The search field is missing a label but has a title and placeholder text. While these can be valuable, they are not a replacement for labels and are not treated as such by assistive technologies. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions).

Skip to content

There is also no option to skip repeated content. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

Status message

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

Disproportionate burden

Not applicable.

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

This section covers issues that we do not need to fix right now. The law calls these exemptions.

Documents published before 23 September 2018

The accessibility regulations do not require us to fix documents published before 23 September 2018 if they are not essential to someone accessing our services.

Many of our older documents do not meet accessibility standards - for example, they may not be tagged so they’re accessible to some using a screen reader. Contact us to request an accessible alternative to one of these documents.

Read about what we are doing to improve the accessibility of documents.

Third-party content

Our website uses functionality and content that is neither funded, developed or under our control. This means we cannot always guarantee they will be accessible.

The following third-party content and functionality that we use have known accessibility issues.

Air-quality in Hammersmith & Fulham widget

Routes are only provided on the map and no text descriptions are given.

Google Translate

The dropdown box to select a language is missing a label.

Twitter timeline widgets

The buttons for liking and sharing tweets cannot be selected using a keyboard accessible and don't receive focus when they are tabbed to.

Videos published before 23 September 2020

Video content embedded on our website before 23 September 2020 may not meet accessibility standards.

This is because they may not feature:

  • subtitles or captions
  • an audio-description
  • a written transcript

While these videos are not subject to the regulations, we are adding text alternatives where possible.

How we monitor this website

We use Silktide an automated testing tool to help us monitor and fix usability and accessibility issues as they occur.

We also use a range of other tools to test for accessibility issues including:

  • Accessibility insights for the web
  • Arc toolkit
  • Axe
  • browser developer tools
  • NVDA
  • Siteimprove accessibility checker
  • Text spacing
  • WAVE
  • Web Aim contrast checkers
  • Web developer

Manual reviews are carried to assess any content and functionality automated testing cannot cover.

What we’re doing to improve accessibility

Documents

We’re working with our service teams to provide an accessible HTML version of any new information as the primary source rather than use a PDF or other document formats.

Any new PDFs or documents we publish, that we own or control, will meet accessibility standards. If we have to publish a PDF that doesn’t meet accessibility standards, we will provide a plain text version that does.

We also have a register of all the documents on our website and are reviewing them to see which ones we can convert to HTML content now or when we upgrade our website later this year. Our new website will have improved functionality allowing us to publish longer-form content more easily on web pages and overall reduce the need to use PDFs.

Videos

New videos used on our website will be published to their own page and include a transcript on this page.

Preparation of this accessibility statement

This statement was prepared on 23 September 2019. It was last reviewed on 6 April 2021.

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