Accessibility statement for the visitor parking permit system
This service is part of the wider H&F website and is run by Hammersmith & Fulham Council through our third party supplier, RingGo.
Using this website
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
- 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 such as form fields and links do not meet minimum colour contrast requirements
- error messages and instructions are not associated with form forms or labels and may be missed by screen reader users
- the site has horizontal scrolling on mobile devices and when zoomed up to 200%
- images may contain text that hasn't been included on the page
- multiple H1 headings are used on each page
- the search fields are missing labels.
Feedback and contact information
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.
- call us on 020 7371 5678
- email us at firstname.lastname@example.org
Reporting accessibility problems with this service
We're always looking to improve the accessibility of the visitor parking permit 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.
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.
Technical information about this website’s accessibility
Hammersmith & Fulham is committed to making the visitor parking permit system accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some elements do not meet minimum colour contrast requirements. This includes the:
- focus style of the navigation tabs
- focus style of some buttons
- footer links
- asterisks (*) in form field labels
- error summary message.
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).
On the help centre page, some links are only identifiable by colour and don’t meet the minimum colour contrast ratio needed between links and surrounding text. This fails WCAG 2.1 success criterion 1.4.1 (use of colour).
Images, video and audio content
An image has been used to show step by step instructions on the Westfield Blue Badge RVP permit information page, but there is no text equivalent. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
Interactive tools and transactions
Autocomplete tokens have been set to "off" on 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.
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, instructions and notes. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
Important information such as error and success messages and the number of parking transactions found are not marked up in a way so they can be read out by assistive technologies. This fails WCAG 2.1 success criterion 4.1.3 (status message).
The error messages provided don't give any suggestions on how to correct invalid entries. This fails WCAG 2.1 success criterion 3.3.3 (error suggestion).
The text explaining that a form label with an asterisk (*) is required is positioned after the buttons at the bottom of the page. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions).
Checking the 'Use a landline' checkbox changes the labels for the fields above it but not all users will be aware of this. This fails WCAG 2.1 success criterion 3.3.2 (labels or instructions).
The CAPTCHA used does not offer alternative methods for validation and relies on users to check a box. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
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 main content is not included in a landmark when other sections of the page are. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 2.4.1 (bypass blocks).
The search field in the header and on the help centre page are missing labels. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and 3.3.2 (labels or instructions).
The search button in the header 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).
Every page has the same page title meaning assistive technology users may struggle to discern what page they are actually on. This fails WCAG 2.1 success criterion 2.4.2 (page titled).
Some content and functionality doesn't reflow into a single column when zoomed at 200% or viewed on mobile devices and requires horizontal scrolling. This fails WCAG 2.1 success criterion 1.4.4 (resize of text) and 1.4.10 (reflow).
The date picker on the monthly statements page is not accessible to keyboard only users. This fails WCAG 2.1 success criterion 2.1.1 (keyboard).
The tab focus order doesn’t follow a logical sequence in the header navigation. This is not compliant with WCAG 2.1 guideline 2.4.3 (focus order).
Text, links and tables
Multiple H1 headings are used on most pages. 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).
Some of the social media icons are missing from the footer although the links to the sites are there. The links are also empty meaning their purpose is not presented to assistive technology users. These issues fail WCAG 2.1 success criterion 1.1.1 (non-text content) and 2.4.4 (link purpose - in context).
The desktop and mobile search fields in the header both have the same ID. This fails WCAG 2.1 success criterion 4.1.1 (parsing).
Content that’s not within the scope of the accessibility regulations
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
- Text spacing
- Web developer.
What we’re doing to improve accessibility
We're working with the supplier, RingGo, 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.