[Skip navigation links]

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.

LevelWCAG 2.1Section 508 - 2017Key
ALevel A, 11 issuesLevel A, 11 issuesCritical Pages with level A issues are unusable for some people
AALevel AA, 1 issuesLevel AA, 1 issuesVery Important Pages with level AA issues are very difficult to use
AAALevel AAA, 4 issuesLess Important Pages with level AAA issues can be difficult to use
PriorityDescription and URLGuideline and Line#Count

Level A

11 issues on 6 pages

Criticalalt text should not be a meaningless image file name. WCAG 2.1 A F30 Section 508 (2017) A F30 2 pages
Change the alt text to describe the information or function represented by the image, and for purely decorative images use alt="" without any global ARIA attributes. Do not use alt text containing only spaces since that's voiced as an unlabeled image. 1.1.1
alt='bullet' alt='bullet'
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 300 300
alt='bullet' alt='bullet'
https://www.w3.org/WAI/demos/bad/before/home.html
Line 299 299
Criticalalt text should not contain placeholders like 'picture' or 'spacer'. WCAG 2.1 A F30 Section 508 (2017) A F30 2 pages
For purely decorative images and spacers use alt='', for images of text use the text, and for other images use a description of the image.

Impact on users:

  • JAWS : Reads out placeholder text, instead of a useful image description.
  • NVDA : Reads out placeholder text, instead of a useful image description.
  • VoiceOver : Reads out placeholder text, instead of a useful image description.
1.1.1 1.2.1
alt='bullet' alt='bullet'
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 300 300
alt='bullet' alt='bullet'
https://www.w3.org/WAI/demos/bad/before/home.html
Line 299 299
CriticalHTML form control has no accessible name. WCAG 2.1 A F68 Section 508 (2017) A F68 6 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
4.1.2
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 189
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 188
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 89
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 84
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalIdentify 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 6 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.
1.3.1
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 172 173 214 244 305 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 213 243 304 317 338 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 72 114 144 189 209 ...
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 109 139 191 205 264 ...
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
Criticalimg elements must have an accessible name. WCAG 2.1 A F65 Section 508 (2017) A F65 6 pages
Add an alt attribute describing the image, which screen readers voice instead of the image. Spacer images and purely decorative images should use alt="" without any global ARIA attributes. Do not use alt text containing only spaces since that's voiced as an unlabeled image.

Impact on users:

  • NVDA 2023.3 Chrome 120 Windows 10 Reading: Image ignored.
  • NVDA 2023.3 FF 115 Windows 10 Reading: Image ignored.
  • NVDA 2023.3 Edge 120 Windows 10 Reading: Image ignored.
  • JAWS 2023.2311.34 Chrome 120 Windows 10 Reading: Image ignored.
  • JAWS 2023.2311.34 FF 115 Windows 10 Reading: Image ignored.
  • JAWS 2023.2311.34 Edge 120 Windows 10 Reading: Image ignored.
  • VoiceOver macOS 13.6 Safari 16.6 macOS 13.6.0 Reading: Image filename read out.
  • VoiceOver iOS 16.6 Safari iOS 16.6 iOS 16.6.1 Touch: Image filename read out, along with OCR text from image.
1.1.1
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 185 186 275 303 335 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 185 274 302 313 334 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 76 80 85 86 175 ...
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 71 80 81 170 172 ...
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalIndicating links using only a text color change does not work for color-blind users. WCAG 2.1 A F73 Section 508 (2017) A F73 4 pages
Remove the text-decoration:none property from your link styles, or add other style attributes in addition to color changes to make links visible to people without color vision. If the non-color cue only happens when the mouse hovers over the link or when the link receives focus, it is still a failure. 1.4.1
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 300 300 320 341
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 299 299 319 340
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 184 187
https://www.w3.org/WAI/demos/bad/before/template.htmlLine 187 208
CriticalLinks must have an accessible name. WCAG 2.1 A F89 Section 508 (2017) A F89 6 pages

A link name allows screen readers to voice what the links does. If there is no link content, or the link content is hidden by CSS, 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 labeling the link if it contains an img element
img elements with role=presentation or role=none are not included in the link's accessible name.
2.4.4 2.4.9 4.1.2
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 250 256 262 294 296 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 249 255 293 294 295 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 150 156 162 168
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 145 151 157 163
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
Criticalselect lists cannot be operated from the keyboard if they have a change handler that performs navigation, because the handler fires as the user moves the selection up and down using the keyboard. WCAG 2.1 A 3.2.2 Section 508 (2017) A 3.2.2 6 pages
Moving through list items using the arrow keys will jump to another page unexpectedly.
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 189
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 188
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 89
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 84
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalThis field removes focus when tabbed to making it impossible for disabled users to navigate this form via the keyboard. WCAG 2.1 A F55 Section 508 (2017) A F55 6 pages
Using blur() in an onfocus handler makes the form impossible to use with a keyboard. Remove the call to blur() in the onfocus handler. 2.1.1 2.1.3 2.4.7 3.2.1
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 282 283 284 296 341 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 281 282 283 294 295 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 150 156 162 168
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 145 151 157 163
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalThis page uses nested tables, which do not make sense when read in a screen reader. WCAG 2.1 A F49 Section 508 (2017) A F49 6 pages
Add role='presentation' if the inner table is a layout table, otherwise modify the inner table to present the same data without nesting tables. 1.3.2
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 173 214 241 244 305 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 213 243 304 317 338 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 73 114 144 189 209 ...
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 68 109 139 199 205 ...
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalUse the lang attribute to identify the language of the page. WCAG 2.1 A 3.1.1 Section 508 (2017) A 3.1.1 6 pages
In HTML add a lang attribute containing a language code to the html tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly.
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 1
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 2
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 1
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 1
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.

Level AA

1 issues on 6 pages

Very ImportantEnsure that text and background colors have enough contrast. WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3 6 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
1.4.6
The text color to background color contrast ratio after composition is: 2.76 with color: rgb(255,0,0)background: rgb(215,215,205)font-size: 12ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 400 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 400 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 700
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 143 311 311 332 332
The text color to background color contrast ratio after composition is: 2.76 with color: rgb(255,0,0)background: rgb(215,215,205)font-size: 12ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 400 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 400 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 10.67ptfont-weight: 700
https://www.w3.org/WAI/demos/bad/before/home.html
Line 144 310 310 331 331
The text color to background color contrast ratio after composition is: 2.76 with color: rgb(255,0,0)background: rgb(215,215,205)font-size: 12ptfont-weight: 700
https://www.w3.org/WAI/demos/bad/before/news.html
Line 45
The text color to background color contrast ratio after composition is: 2.76 with color: rgb(255,0,0)background: rgb(215,215,205)font-size: 12ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 9ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 9ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 9ptfont-weight: 700 3.88 with color: rgb(65,84,93)background: rgb(169,184,191)font-size: 9ptfont-weight: 700
https://www.w3.org/WAI/demos/bad/before/tickets.html
Line 40 207 208 209 210 ...
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.

Level AAA

4 issues on 7 pages

ImportantAvoid specifying a new window as the target of a link with target=_blank. WCAG 2.1 AAA F22 2 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 an "opens in a new window" warning into the link text or add the warning to the link using a title attribute or aria-describedby attribute. 3.2.5
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 300 300
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 299 299
ImportantEnsure that text and background colors have a 7:1 contrast ratio. WCAG 2.1 AAA 1.4.6 6 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 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 after composition is: 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 5.83 with color: rgb(34,108,142)background: rgb(255,255,255)font-size: 12ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 5.83 with color: rgb(34,108,142)background: rgb(255,255,255)font-size: 12ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 320 341 352 352 352 ...
The text color to background color contrast ratio after composition is: 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 5.83 with color: rgb(34,108,142)background: rgb(255,255,255)font-size: 12ptfont-weight: 400 5.83 with color: rgb(34,108,142)background: rgb(255,255,255)font-size: 12ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 5.83 with color: rgb(34,108,142)background: rgb(255,255,255)font-size: 11.25ptfont-weight: 400
https://www.w3.org/WAI/demos/bad/before/home.html
Line 299 319 340 351 351 ...
The text color to background color contrast ratio after composition is: 6.77 with color: rgb(65,84,93)background: rgb(237,237,237)font-size: 12ptfont-weight: 400 6.77 with color: rgb(65,84,93)background: rgb(237,237,237)font-size: 10.67ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400
https://www.w3.org/WAI/demos/bad/before/news.html
Line 196 218 260 260 260 ...
The text color to background color contrast ratio after composition is: 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400 4.98 with color: rgb(34,108,142)background: rgb(237,237,237)font-size: 9ptfont-weight: 400
https://www.w3.org/WAI/demos/bad/before/tickets.html
Line 279 279 279 279 279
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
ImportantLink uses general text like 'Click Here' which doesn't explain link purpose. WCAG 2.1 AAA F84 3 pages
Screen reader users often tab from one link to the next, or use the 'Next Link' command. Moving between links labelled 'click here' sounds like 'Click here, tab, click here, tab, click here'. Change the link text, or add an aria-label, so the link makes sense when read without the surrounding text. 2.4.9
Link text: Read More... Read More... Click here Click here
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 300 300 320 341
Link text: Read More... Read More... Click here Click here
https://www.w3.org/WAI/demos/bad/before/home.html
Line 299 299 319 340
Link text: Read more... Read more...
https://www.w3.org/WAI/demos/bad/before/template.html
Line 187 208
ImportantSeveral links on a page share the same link text, but go to different destinations. WCAG 2.1 AAA 2.4.9 2 pages
Make the link text unique for each target, or add additional text using aria-label.
Link text: Read More... Read More...
https://www.w3.org/WAI/demos/bad/before/home.html
Line 319 340
Link text: Home Page Home Page
https://www.w3.org/WAI/demos/bad/before/reports/home.html
Line 63 75

Informative

These messages are for information only and do not indicate errors or conformance problems

InformationWCAG Success Criteria 4.1.1 is always satisfied for HTML and XML pages. WCAG 2.1 4.1.1 1 pages
Since WCAG 2 4.1.1 was written, the HTML Standard has added requirements specifying exactly how browsers handle incomplete markup, incorrectly nested elements, duplicate attributes, and duplicate IDs. This means the "except where the specifications allow" condition in 4.1.1 is satisfied.
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 1
Expand all 17 issues