Accessibility statement for the parking permit application system

This accessibility statement applies to the parking permit application system. There’s a separate accessibility statement for the main H&F website.

This service is part of the wider H&F website and is run by Hammersmith & Fulham Council through our third party supplier, Conduent

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

  • change colours, contrast levels and fonts
  • zoom in up to 200% without the text spilling off the screen
  • get from the start of the service to the end using just a keyboard
  • get from the start of the service to the end using speech recognition software
  • listen to the service 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 service are not fully accessible:

  • some elements such as form fields and links do not meet minimum colour contrast requirements
  • the tab order doesn't follow a logical sequence and may confuse users
  • some form fields are missing labels
  • error messages and instructions are not associated with form forms or labels and may be missed by screen reader users
  • the language setting for the system has not been defined.

What to do if you're having difficulty using this service

Contact us if you need help using this service or information in a different format like accessible PDF, large print, easy read, audio recording or braille.

You can:

  • call us on 020 8753 6681
  • email us at parkingpermits@lbhf.gov.uk
  • write to us at H&F Direct, Pay and Park (AT), PO Box 60820, London, W6 9UZ.

Reporting accessibility problems with this service

We're always looking to improve the accessibility of the parking permit application system.

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

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.

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

Non-accessible content

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

Non-compliance with the accessibility regulations

Colour contrast

Some elements do not meet minimum colour contrast requirements. This includes the:

  • focus style of the navigation tabs
  • footer links
  • asterisks (*) in form field labels
  • headings on summary tables

These issues fail WCAG 2.1 success criterion 1.4.3 (contrast - minimum).

Form fields also do not meet minimum colour contrast requirements. This fails WCAG 2.1 success criterion 1.4.11 (non-text contrast).

Interactive tools and transactions

Autocomplete tokens are not used on any relevant form fields. This fails WCAG 2.1 success criterion 1.3.5 (identify input purpose). Modern browsers such as Chrome will still offer users autocomplete options on appropriate fields.

Not all error messages provide suggestions on how to correct invalid entries. This fails WCAG 2.1 success criterion 3.3.3 (error suggestion).

Some information is not displayed in form labels or programmatically associated with form fields meaning assistive technology users may not know about them. This includes error messages and instructions such what file types and file size can be uploaded to permit applications. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

The instructions on what format to enter the applicant's date are provided as placeholder text in the form field. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions).

Important messages appear on screen that are not marked up in a way that assistive technology users will be aware of them. This fails WCAG 2.1 success criterion 4.1.3 (status message).

Some form fields are missing labels or are not correctly associated with labels. There are also fieldsets used that don't include legends. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

Language

The language setting has not been specified for system. This fails WCAG 2.1 success criterion 3.1.1 (language of page).

Navigation and accessing information

No skip to main content link is provided. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).

The search field is missing a label. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

The search button doesn’t have a name meaning its purpose won’t be presented to assistive technology users. This fails WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).

Technology

The tab focus order has been altered meaning it doesn't follow a logical sequence with what's visually presented or between related form fields.

For example the tab sequence:

  • starts in the main content section and then goes to the header section
  • on the permit details page jumps around in the sections about providing proof of a driving licence and if the applicant has an electric vehicle.

This fails WCAG 2.1 success criterion 2.4.3 (focus order).

The date picker that can be used to enter the applicant's date of birth is not accessible from a keyboard. This fails WCAG 2.1 success criterion 2.1.1 (keyboard).

Text, links and tables

The H&F logo in the header does not have descriptive alternative text, while the H&F logo in the footer is a link but is missing alternative text meaning the purpose of the image is not presented to assistive technologies. These issues fail WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).

The social media icons in the footer are empty links meaning their purpose is not presented to assistive technology users. This fails WCAG 2.1 success criterion 2.4.4 (link purpose - in context).

Website code

The desktop and mobile search fields both have the same ID. This fails WCAG 2.1 success criterion 4.1.1 (parsing).

Disproportionate burden

Not applicable.

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

Not applicable.

How we tested this service

This service was last tested on 21 September 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 working with the supplier, Conduent, 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.