Accessibility statement

4. Technical information about this website’s accessibility

As part of our commitment to accessibility we are required to publish where we know there are issues with our website.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the following issues.

Images

Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This does not meet WCAG success criterion 1.4.5 (Images of Text).

We are working to remove all images that contain text. When we publish new content we’ll make sure our use of images meets accessibility standards.

Links

For some of our links that contain images, link text matches the image alt text. This does not comply with WCAG 2.0 A H2.

Iframes

Some of the iFrames on the forms do not have a title attribute. This does not meet WCAG 2.1 success criterion 2.4.1 (Bypass blocks) and WCAG 2.1 success criterion 4.1.2 (Name, Role, Value – Frames must have a title attribute).

We are migrating our website to the GOV.UK framework to address this issue.

Forms

One of our controls has a blank label or title, this does not comply with WCAG 2.0 A F68.

Some of our forms have duplicate field labels, making it difficult to identify their purpose. This does not meet WCAG 2.1 AA success criterion 2.4.6 (Headings and Labels).

We are migrating our website to the GOV.UK framework to address this issue.

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services, but may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, role value).

We are working to either fix these or replace them with accessible HTML pages. Any new PDFs or Word documents we publish should meet accessibility standards.

Other web development issues

  • On some pages the italics-tag ‘i’ is used to highlight text. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (1.3.1 information and relationships). We are working to remove italics tags, (except where they are necessary for a legal term).
  • On some pages, the div and ul elements have been nested as children where they shouldn’t be. This does not comply with HTML5 WCAG 2.0 A 4.1.1. This will be addressed by the migration to the new website.
  • On one page a duplicate ID has been used on more than one element. This does not comply with HTML5 WCAG 2.0 A 4.1.1. This will be addressed by the migration to the new website.

Special sections of the site

Payment pages

Some of our forms use the same ID is used on more than one element. This means that users of assistive technologies will not be able to identify the unique purpose of the form field. This does not meet success criterion WCAG 2.1 A 4.1.1.

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

Some pages use CSS to markup bold text instead of using semantic markup. This means that changes in text to convey meaning will not be picked up by assistive technology. This does not comply with WCAG 2.1 A F2.

Schools appeal pages

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

Some of our forms have duplicate field labels. This means that it is difficult to identify their purpose. This does not meet with success criterion WCAG 2.0 AA 2.4.6.

Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

The focus outline styling has been switched off through CSS. This means that users cannot see where they are on the page when they tab through links. This does not comply with WCAG 2.1 AA F78.

Freedom of Information pages

The iframes which embeds the Freedom of Information form do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Rights of Way maps

Search results pages have the same title, making it difficult to distinguish pages. This does not comply with WCAG 2.1 A F25.

The code (WAI-ARIA) which is used by screen readers is incorrect or redundant. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role, value).

Support with Confidence

Some of our forms use the same ID on more than one element. This means that users of assistive technologies will not be able to identify the unique purpose of the form field. This does not meet success criterion WCAG 2.1 A 4.1.1.

Some of our form fields and buttons are not labelled correctly. This means some users will not be able to identify the purpose of the form field. This does not comply with WCAG 2.1 A F68.

Some iframes do not have a title. This means that assistive technologies will read out the frame filename, which may be meaningless. This does not meet with success criterion WCAG 2.1 A 2.4.1.

Search results pages have the same title, making it difficult to distinguish pages. This does not comply with WCAG 2.1 A F25.

Some of our forms have duplicate field labels. This means that it is difficult to identify their purpose. This does not meet with success criterion WCAG 2.0 AA 2.4.6.

These issues will be addressed in-house. See What we’re doing to improve accessibility.

Penalty Charge Notice (PCN) viewer

1.1.1 Non-Text Content
There are some personal data fields on the ‘Making a Representation’ screen that do not read out the name of the field whilst using a screen reader (NVDA).

1.2.1 Audio-only and Video-only (Pre-recorded)
1.2.2 Captions (Pre-recorded)
1.2.3 Audio Description or Media Alternative (Pre-recorded)
Images and videos are uploaded onto the portal, as part of evidence of a contravention. However, a user that relies on text-to-speech programs will not be able to watch the video. As well – a user that cannot hear audio (if any are present) will have difficulty. All videos, images, and audio must be made more accessible via text alternatives.

1.4.3 Contrast
Buttons, such as the ‘Pay PCN’ buttons, and the red warning text ‘No mapping data available.’ do not pass the contrast success criteria

2.4.1 Bypass Blocks
Website requires a ‘skip link’ for users that rely on keyboard to skip content such as headers and navigation links.

2.4.4 Link Purpose (In Context)
The final column that is to the right of ‘Street’ in the Pay PCN and Main Display Pages is blank. This is problematic as a user that relies on screen reader technology will not know what that column represents.

2.4.7 Focus Visible
the social media buttons in the website footer and the ‘Online Services’, ‘Contact Us’ and ‘News & Events’ buttons are not being highlighted to indicate their focus when navigating using only the keyboard.

Within the ‘Key Events’ page, there is a table which can’t be focused via tabbing, or strict keyboard use.

3.3.1 Error Identification
There is no error message displayed following the non-upload of file attachments when making a Representation, there is just a coloured border around the Additional Information button.

4.1.1 Parsing
Within the ‘Key Events’ and ‘View Map Location’ pages there is a hidden ID titled ‘SelectedPCNReference’ that is duplicated. This can potentially break accessibility, as screen readers may skip labels, tables etc due to duplicate IDs.

4.1.2 Name, Role, Value
Within the ‘Images’ page on the PayPCN screen, there are two violations. Two listboxes do not have an accessible name:
videoListView and listView.

We plan to rectify all identified issues by 31 March 2021. When we publish new content, we’ll make sure we continue to meet accessibility standards.

Print entire guide