Cookie Consent by Free Privacy Policy Generator website

Accessibility Statement - Parking permits and parking fines

This accessibility statement should be read in relation to our main accessibility statement.

This statement applies to part of our online services available via our website - our 'parking portal' - used to administer parking permits and parking fines (known as penalty charge notices, or PCN); the functionality is provided by Taranto Systems.

We know some parts of this system are not fully accessible, see Technical information about this system's accessibility.

Feedback and contact information for reporting accessibility problems

Get more information about:

Technical information about this system’s accessibility

We are committed to making our online services accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations, 2018.

Compliance status

This part of our website is partially compliant with the Web Content Accessibility Guidelines version 2.2, Level AA due to the non-compliances listed.

Non-compliance with the accessibility regulations

  • Not all Accessible Rich Internet Applications (ARIA) attributes match their roles; ARIA is a set of roles and attributes that make web content and web applications more accessible to people with disabilities - this would be required to meet the WCAG AA standard.
  • The label element may not always explicitly associate a form control with a label - this relates to WCAG, level AA, success criterion 1.1.1.
  • Data cells in data tables may not be associated with appropriate headers, the relationships between content and elements are not always made clear by visual formatting, and some fields are not programmatically associated with the overarching question, and some content (telephone number) is visually styled as regular text whilst programmatically it's a link, all of which means users of assistive technologies may not be able to accurately interpret information - this relates to WCAG, level AA, success criterion 1.3.1.
  • For some form inputs, which ask for personal information, there are no autocomplete attributes and the purpose of components is not programmatically available; the code is not identifying the data it expects, despite this being required for certain input types, and as such filling in forms may be harder for users of assistive technology and those with cognitive impairments - this relates to WCAG, level AA, success criterion 1.3.5.
  • Some links have poor colour contrast, which doesn't meet the minimum ratio, between the text and its background when receiving keyboard focus; this makes it harder for all users to see content - this relates to WCAG, level AA, success criterion 1.4.3.
  • The overall design may not be responsive when accessed using a mobile device; content may appear cut off, or may use scroll bars rather than using layout techniques that adapt to the available space - this relates to WCAG, level AA, success criterion 1.4.4.
  • Not all functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes - this relates to WCAG, level AA, success criterion 2.1.1.
  • The time interval for an automatic page refresh is too short, and there is no way to turn auto-refresh off; users may not have enough time to interact with the web page, and read content before the session expires without warning, and it's not possible to turn off, adjust or extend the time limit - this relates to WCAG, level AA, success criteria 2.2.1, 2.2.4, and 3.2.5.
  • The first interactive item within pages is not always a link to the beginning of the main content - this relates to WCAG, level AA, success criterion 2.4.1.
  • Some pages do not have descriptive, unique or meaningful titles, so the user is not informed of their position in the application process and the topic or purpose of the page is not described in the browser tab or window title bar - this relates to WCAG, level AA, success criterion 2.4.2.
  • It's not always possible for keyboard-only users to navigate within tables using the keyboard - this relates to WCAG, level AA, success criterion 2.4.3.
  • It's sometimes difficult to determine visually if a checkbox has been selected - this relates to WCAG, level AA, success criterion 2.4.13.
  • There are some links which are ambiguous, where context is missing programmatically (despite being visually clear), and some icons which have misleading names, meaning the purpose of navigation is not clear from the link text alone, or from its immediate context; this directly misinforms users of assistive technology or those using tab-navigation - this relates to WCAG, level AA, success criterion 2.4.4.
  • Some button, link, and menu item elements do not have accessible names - this relates to WCAG, level AA, success criterion 2.5.3.
  • Not all ARIA commands have an accessible name - this relates to WCAG, level AA, success criterion 2.5.3.
  • Potential confusion can be caused by unexpected changes of context, such as automatic launching of new windows and automatic submission of forms after selecting an item from a list, this may cause difficulties for people with motor impairments, people with low vision, people who are blind, and people with certain cognitive limitations - this relates to WCAG, level AA, success criterion 3.2.5.
  • There are some instances, if a user makes an error when submitting a form, that they aren't made aware of one or more of the errors, so they may find it hard to identify what is wrong and why they can't progress - this relates to WCAG, level AA, success criterion 3.3.1.
  • Some links in navigation menus are visually hidden but not programmatically hidden, meaning they are available to users of assistive technology, but whilst having no accessible name or ARIA attributes, as such, using menu navigation may be harder for users of assistive technology and those with cognitive impairments; there are some form fields which do not use programmatic information to inform users of assistive technology that the fields are invalid when an error message appears visually as such filling in forms may be harder for users of assistive technology and those with cognitive impairments - this relates to WCAG, level AA, success criterion 4.1.2.
  • There are some error messages and some status messages which are not announced to inform users of assistive technology of the error or status, as such they may not be aware that the action or input was unsuccessful- this relates to WCAG, level AA, success criterion 4.1.3.

What we’re doing to improve accessibility

We have identified areas of this system that need to be addressed in order to meet the Web Content Accessibility Guidelines. We're working with our suppliers to rectify known issues as soon as possible.

Preparation of this accessibility statement

This statement was last reviewed on 1 May 2025.

This system was last tested during October 2024, by the Accessibility Monitoring Team in Cabinet Office, with both manual and automated sample testing using web developer extensions Axe and WAVE, as well as Adobe Acrobat Pro and WebAIM Contrast Checker.

Further accessibility fixes to address non-accessible aspects of this system are expected by 30 December 2025.

Also see

Comment on this page