Accessibility statement for the Challenge a PCN system

This accessibility statement applies to the Challenge a PCN 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 website are not fully accessible:

  • some elements do not meet minimum colour contrast requirements
  • there no way to skip repeated links
  • form fields do not have labels
  • important messages are not marked up for screen readers to read them out
  • error messages and hint text are not associated with form fields

Feedback and contact information

If you need help using this service email us at enquiries@lbhfparking.com

Reporting accessibility problems with this service

We're always looking to improve the accessibility of the Challenge a PCN 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).

Technical information about this website’s accessibility

Hammersmith & Fulham Council is committed to making the Challenge a PCN system 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
  • error messages

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

Interactive tools and transactions

The form fields on the start page do not have labels. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).

The labels that should be associated with the form fields on are start page are associated with non-existent form controls. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

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 hint text. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

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

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 order in the header doesn't follow a logical sequence with what's visually presented. This fails WCAG 2.1 success criterion 2.4.3 (focus order).

Heading tags have been used incorrectly to style text when CSS should be used. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).

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

When the CSS is disabled, the error messages for the form fields on the start page are displayed as normal. This fails WCAG 2.1 success criterion 1.3.2 (meaningful sequence).

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 1 July 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 9 April 2021.

Translate this website