Site Report
This tab shows accessibility issues, indicating problems for older users, people with disabilities or accessibility needs. Automated testing cannot detect all accessibility issues, so should be used alongside human testing.
| Level | WCAG 2.1 | Section 508 - 2017 | Key |
|---|
| A |  | | Pages with level A issues are unusable for some people |
|---|
| AA |  | | Pages with level AA issues are very difficult to use |
|---|
| AAA |  | | Pages with level AAA issues can be difficult to use |
|---|
| Priority | Description and URL | Guideline and Line# | Count |
|---|
Level A
7 issues on 1 pages | |
| | All fieldset elements should be labeled with legend elements. | WCAG 2.1 A H71 Section 508 (2017) A H71 | 1 pages |
|
The first child element inside a fieldset must be a legend element, which provides a label or description for the group. legend elements in other positions may be ignored. | | |
| https://parking.liverpool.gov.uk/pcn/ | Line 59 | |
| | Each a element must contain text or an img with an alt attribute. | WCAG 2.1 A F89 Section 508 (2017) A F89 | 1 pages |
|
A link name allows screen readers to voice what the links does. If there is no link text or the `alt` text is blank, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following:
- Add text between the
a element start and end tags
- Add an
aria-label attribute
- Add an
aria-labelledby attribute
- Add an
img alt attribute if the link contains an img element
| | |
| https://parking.liverpool.gov.uk/pcn/ | Line 73 307 | |
| | HTML form control has no label. | WCAG 2.1 A F68 Section 508 (2017) A F68 | 1 pages |
|
A label (or name) linked to the control allows screen readers to voice the label correctly when reading the control. To add a label do one of the following:
- Use a
label element with the for attribute set to the ID of the form control
- Wrap a
label element around the form control
- Add a
title attribute
- Add an
aria-label attribute
- Add an
aria-labelledby attribute
| | |
| https://parking.liverpool.gov.uk/pcn/ | Line 95 | |
| | Identify row and column headers in data tables using th elements, and mark layout tables with role=presentation. | WCAG 2.1 A F91 Section 508 (2017) A F91 | 1 pages |
|
Data tables allow screen reader users to understand column and row relationships.
Layout tables read cells as a series of unrelated paragraphs with no tabular structure.
Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table.
These heuristics vary greatly between screen readers, and are affected by browser being used, window size,
and font size (so the outcome is very unpredictable without TH or ROLE).
If a data table has headers marked up using TD, then change these to TH.
If a data table has no headers, add TH elements describing each row and/or column.
If the table is only used for layout add role='presentation' to the TABLE element.
Impact on users: - JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
- NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
- VoiceOver Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
| | |
| https://parking.liverpool.gov.uk/pcn/ | Line 136 152 173 | |
| | This form control has a blank label or title. | WCAG 2.1 A F68 Section 508 (2017) A F68 | 1 pages |
|
Add descriptive text to the form control's label. | | |
| https://parking.liverpool.gov.uk/pcn/ | Line 95 | |
| | This page has markup errors, causing screen readers to miss content. | WCAG 2.1 A F70 Section 508 (2017) A F70 | 1 pages |
|
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content. | | |
| https://parking.liverpool.gov.uk/pcn/ | Line 3 | |
| | img elements must have an alt attribute. | WCAG 2.1 A F65 Section 508 (2017) A F65 | 1 pages |
|
Add an alt attribute describing each image, which a screen reader voices instead of the image.
Spacer images and purely decorative images should use alt="".
Impact on users: - NVDA 2019.2 Chrome 79 Windows 10 Reading: Image unlabeled.
- NVDA 2019.2 FF68 Windows 10 Reading: Image ignored.
- NVDA 2019.2 IE11 Windows 10 Reading: Image ignored.
- NVDA 2018.4 Chrome 73 Windows 10 Reading: Image ignored.
- NVDA 2018.4 FF60 Windows 10 Reading: Image ignored.
- NVDA 2018.4 IE11 Windows 10 Reading: Image ignored.
- JAWS 2019.1912.1 Chrome 79 Windows 10 Reading: Image unlabeled.
- JAWS 2019.1912.1 FF68 Windows 10 Reading: Image ignored.
- JAWS 2019.1912.1 IE11 Windows 10 Reading: Image ignored.
- JAWS 2018.1811.2 Chrome 73 Windows 10 Reading: Image ignored.
- JAWS 2018.1811.2 FF60 Windows 10 Reading: Image ignored.
- JAWS 2018.1811.2 IE11 Windows 10 Reading: Image ignored.
- VoiceOver macOS 10.14 Safari 13.0 macOS 10.14.6 Reading: Image filename read out.
- VoiceOver macOS 10.13 Safari 12.1 macOS 10.13.6 Reading: Image filename read out.
- VoiceOver macOS 10.12 Safari 10.1.2 macOS 10.12.6 Reading: Image filename read out.
- VoiceOver iOS 12.4 Safari iOS 12.4 iOS 12.4.1 Touch: Image filename read out.
- VoiceOver iOS 11.4 Safari iOS 11.4 iOS 11.4.1 Touch: Image filename read out.
- VoiceOver iOS 10.3 Safari iOS 10.3 iOS 10.3 Touch: Image filename read out.
| | |
| https://parking.liverpool.gov.uk/pcn/ | Line 91 | |
Level AA
3 issues on 2 pages | |
| | Ensure that text and background colors have enough contrast. | WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3 | 1 pages |
|
Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.
- The contrast ratio should be 3.0 or more for 18 point text, or larger
- The contrast ratio should be 3.0 or more for 14 point bold text, or larger
- The contrast ratio should be 4.5 or more for all other text
| | |
|
The text color to background color contrast ratio is:
1.11 with
color: rgb(233,233,233);
background-color: rgb(245,245,245);
font-size: 9.75pt;
font-weight: 400.00;
1.09 with
color: rgb(255,255,255);
background-color: rgb(245,245,245);
font-size: 9.75pt;
font-weight: 500.00;
1.09 with
color: rgb(255,255,255);
background-color: rgb(245,245,245);
font-size: 9.75pt;
font-weight: 500.00;
1.47 with
color: rgb(204,204,204);
background-color: rgb(245,245,245);
font-size: 9.75pt;
font-weight: 400.00;
1.47 with
color: rgb(204,204,204);
background-color: rgb(245,245,245);
font-size: 9.75pt;
font-weight: 400.00;
https://parking.liverpool.gov.uk/pcn/ | Line 112 112 115 115 117 | |
| | The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. | WCAG 2.1 AA F78 Section 508 (2017) AA F78 | 1 pages |
|
Change the style to avoid obscuring the focus outline around focusable elements.
Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in:
- Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls)
- Firefox (obscures the focus indicator on links)
- Internet Explorer (obscures the focus indicator on links, buttons and range controls)
Internet Explorer does not support the `outline-offset:` property, so using this does not reliably avoid focus outline overlap.
| | |
| https://parking.liverpool.gov.uk/pcn/style/bootstrap.css | Line 1226 | |
| | User interface controls must have a contrast ratio of at least 3:1 against adjacent colors. | WCAG 2.1 1.4.11 | 1 pages |
|
If the control has a visible edge, make sure this has sufficient contrast against the area outside the control. | | |
| The contrast ratio between the control edge and surrounding area is: 1.61 1.61
https://parking.liverpool.gov.uk/pcn/ | Line 159 167 | |
Level AAA
3 issues on 65 pages | |
| | Avoid specifying a new window as the target of a link with target=_blank. | WCAG 2.1 AAA F22 | 62 pages |
|
Displaying new windows without warning can be very confusing to non-sighted and mobile users.
Some screen readers and mobile devices give very little indication a new tab or window has opened.
If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".
| | |
| https://parking.liverpool.gov.uk/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/Account/LoginPage | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/a-z/?letter=a | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/a-z/?letter=b | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/a-z/?letter=c | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/a-z/?letter=d | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/a-z/?letter=e | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/assets/images/logo_white_2x.png | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/business/licences-and-permits/roads-and-highway-licences/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/blue-badges-and-disabled-parking/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/find-parking/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/getting-around-liverpool/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/parking-fines-and-challenges/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/parking-outside-your-home/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/parking-permits/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/public-rights-of-way/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/report-an-issue/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/parking-roads-and-travel/winter-gritting/ | Line 320 321 322 336 | |
| https://parking.liverpool.gov.uk/support/accessibility/ | Line 320 321 322 336 | |
| This issue was found on another 42 pages. You can change the number of pages shown for each issue using the Options menu command in the desktop edition or the Edit Scan button in the OnDemand edition. | | |
| | Don't use CSS animations or transitions in interactions without giving the user a way to turn them off. | WCAG 2.1 2.3.3 | 2 pages |
|
Use the @media (prefers-reduced-motion) media query to respect user preferences. | | |
| https://parking.liverpool.gov.uk/pcn/style/bootstrap-overrides.css | Line 224 377 | |
| https://parking.liverpool.gov.uk/pcn/style/bootstrap.css | Line 1207 4067 4230 5130 | |
| | Ensure that text and background colors have a 7:1 contrast ratio. | WCAG 2.1 AAA 1.4.6 | 1 pages |
|
Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.
Note: The default link color in IE11 has poor contrast on a white background. Fix by specifying a:link and a:visited colors in CSS.
- The contrast ratio should be 4.5 or more for 18 point text, or larger
- The contrast ratio should be 4.5 or more for 14 point bold text, or larger
- The contrast ratio should be 7.0 or more for all other text
| | |
|
The text color to background color contrast ratio is:
5.08 with
color: rgb(223,0,0);
background-color: rgb(255,255,255);
font-size: 12.80pt;
font-weight: 400.00;
5.08 with
color: rgb(223,0,0);
background-color: rgb(255,255,255);
font-size: 12.80pt;
font-weight: 400.00;
5.08 with
color: rgb(223,0,0);
background-color: rgb(255,255,255);
font-size: 12.80pt;
font-weight: 400.00;
https://parking.liverpool.gov.uk/pcn/ | Line 143 156 164 | |
| Expand all 13 issues | | |