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 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.
This part of our website is partially compliant with the Web Content Accessibility Guidelines, (WCAG); we've listed non-compliances.
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 2.1 AA standard.
- The label element may not always explicitly associate a form control with a label - this relates to WCAG 2.1 AA Success Criterion 1.1.1 (Technique H44).
- Data cells in data tables may not be associated with appropriate headers - this relates to WCAG 2.1 AA Success Criterion 1.3.1 (Technique H43).
- 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 2.1 AA Success Criterion 1.4.4 (Technique G146).
- Not all functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes - this relates to WCAG 2.1 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 - this relates to WCAG 2.1 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 2.1 AA Success Criterion 2.4.1 (Technique G1).
- It's not always possible for keyboard-only users to navigate within tables using the keyboard - this relates to WCAG 2.1 AA Success Criterion 2.4.3.
- It's sometimes difficult to determine visually if a checkbox has been selected - this relates to WCAG 2.1 AA Success Criterion 2.4.13.
- Some button, link, and menu item elements do not have accessible names - this relates to WCAG 2.1 AA Success Criterion 2.5.3.
- Not all ARIA commands have an accessible name - this relates to WCAG 2.1 AA Success Criterion 2.5.3 (Technique G211).
- 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. Such unexpected changes of context 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 2.1 AA Success Criterion 3.2.5 (Technique H76).
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 prepared on 15 September 2021. It was last reviewed on 5 August 2024.
This system was last tested prior to a supplier-lead upgrade (released 5 August 2024) by City of York Council's Web Services Team, using manual checks, alongside automated sample testing using BrowserStack, Lighthouse and Silktide software.
Further accessibility fixes to address non-accessible aspects of this system is expected by 31 December 2024.