[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, 12 issuesLevel A, 12 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 NumberCount

Level A

12 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
Placeholder alt text: bullet
<img src='../img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 300
Placeholder alt text: bullet
<img src='../img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 300

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

Placeholder alt text: bullet
<img src='./img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 299
Placeholder alt text: bullet
<img src='./img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 299

https://www.w3.org/WAI/demos/bad/before/home.html

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
Placeholder text: bullet
<img src='../img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 300
Placeholder text: bullet
<img src='../img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 300

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

Placeholder text: bullet
<img src='./img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 299
Placeholder text: bullet
<img src='./img/list_bullets.gif' alt='bullet' border='0' align='absmiddle'>
Line 299

https://www.w3.org/WAI/demos/bad/before/home.html

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
<select onchange='location.href = ...'><option selected>...&#62;</option>...</select>
Line 189

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<select onchange='location.href = ...'><option selected>...&#62;</option>...</select>
Line 188

https://www.w3.org/WAI/demos/bad/before/home.html

<select onchange='location.href = ...'><option selected>...&#62;</option>...</select>
Line 89

https://www.w3.org/WAI/demos/bad/before/news.html

<select onchange='location.href = ...'><option selected>...&#62;</option>...</select>
Line 84

https://www.w3.org/WAI/demos/bad/before/tickets.html

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
<table width='100%' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#d7d7cd'>...</table>
Line 172
<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 173
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 182
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 241
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 350

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<table width='100%' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#d7d7cd'>...</table>
Line 171
<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 172
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 181
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 240
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 349

https://www.w3.org/WAI/demos/bad/before/home.html

<table width='100%' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#d7d7cd'>...</table>
Line 72
<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 73
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 82
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 141
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 258

https://www.w3.org/WAI/demos/bad/before/news.html

<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 77
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 277
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px'>...</table>
Line 109
<table width='155px' border='0px' cellspacing='0px' cellpadding='0px'>...</table>
Line 139
<table style='border; border: 1px ...' width='600px'>...</table>
Line 173

https://www.w3.org/WAI/demos/bad/before/tickets.html

This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalIf a table is used for layout, do not use structural markup like th, headers and scope for the purpose of visual formatting. WCAG 2.1 A F46 Section 508 (2017) A F46 1 pages
Change th to td elements and remove headers and scope if this is a layout table. 1.3.1
<th align='left' colspan='2'>Which city do you find is the greenest?...</th>
Line 282
<th align='left' colspan='2'><span>Do you ...?...</span></th>
Line 507

https://www.w3.org/WAI/demos/bad/before/survey.html

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 2024.4 Chrome 131 Windows 10 Reading: Image ignored.
  • NVDA 2024.4 FF 128 Windows 10 Reading: Image ignored.
  • NVDA 2024.4 Edge 131 Windows 10 Reading: Image ignored.
  • JAWS 2024.2409.2 Chrome 131 Windows 10 Reading: Image ignored.
  • JAWS 2024.2409.2 FF 128 Windows 10 Reading: Image ignored.
  • JAWS 2024.2409.2 Edge 131 Windows 10 Reading: Image ignored.
  • VoiceOver macOS 14.6 Safari 17.6 macOS 14.6.1 Reading: Image filename read out.
  • VoiceOver iOS 17.7 Safari iOS 17.7 iOS 17.7.2 Touch: Image filename read out, along with OCR text from image.
1.1.1
<img src='../img/blank_5x5.gif' width='20px' height='5px'>
Line 275
<img src='../img/blank_5x5.gif' width='20px' height='5px'>
Line 303
<img src='../img/teaser_right2.jpg' width='150px' height='154px'>
Line 335
<img src='../img/top_logo_next_end.gif' width='24px' height='86px'>
Line 185
<img src='../img/top_logo_next_start.gif' width='22px' height='86px'>
Line 187

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<img src='./img/blank_5x5.gif' width='20px' height='5px'>
Line 274
<img src='./img/blank_5x5.gif' width='20px' height='5px'>
Line 302
<img src='./img/teaser_right2.jpg' width='150px' height='154px'>
Line 334
<img src='./img/teaser_right1.jpg' width='150px' height='106px'>
Line 313
<img src='./img/headline_middle.gif' width='23' height='24' align='absmiddle'>
Line 281

https://www.w3.org/WAI/demos/bad/before/home.html

<img src='./img/blank_5x5.gif' width='20px' height='5px'>
Line 175
<img height='24' src='./img/headline_middle.gif' width='23' align='absmiddle'>
Line 241
<img src='./img/top_logo_next_end.gif' width='24px' height='86px'>
Line 85
<img src='./img/top_logo_next_start.gif' width='22px' height='86px'>
Line 87
<img src='./img/top_weather.gif' width='128px' height='86px'>
Line 86

https://www.w3.org/WAI/demos/bad/before/news.html

<img src='./img/blank_5x5.gif' width='20px' height='5px'>
Line 170
<img src='./img/top_logo_next_end.gif' width='24px' height='86px'>
Line 80
<img src='./img/top_logo_next_start.gif' width='22px' height='86px'>
Line 82
<img src='./img/top_weather.gif' width='128px' height='86px'>
Line 81
<img src='...f' border='0'>
Line 172

https://www.w3.org/WAI/demos/bad/before/tickets.html

This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
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
<a href='../news/annotations' onfocus='blur();'>...</a>
Line 296
<a href='../news/annotations' onfocus='blur();'>...</a>
Line 294
<a href='...;' onfocus='blur();'>...</a>
Line 250
<a href='...;' onfocus='blur();'>...</a>
Line 256
<a href='...;' onfocus='blur();'>...</a>
Line 262

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<a href='news.html' onfocus='blur();'>...</a>
Line 294
<a href='news.html' onfocus='blur();'>...</a>
Line 295
<a href='news.html' onfocus='blur();'>...</a>
Line 293
<a href='...;' onfocus='blur();'>...</a>
Line 249
<a href='...;' onfocus='blur();'>...</a>
Line 255

https://www.w3.org/WAI/demos/bad/before/home.html

<a href='...;' onfocus='blur();'>...</a>
Line 150
<a href='...;' onfocus='blur();'>...</a>
Line 156
<a href='...;' onfocus='blur();'>...</a>
Line 162
<a href='...;' onfocus='blur();'>...</a>
Line 168

https://www.w3.org/WAI/demos/bad/before/news.html

<a href='...;' onfocus='blur();'>...</a>
Line 145
<a href='...;' onfocus='blur();'>...</a>
Line 151
<a href='...;' onfocus='blur();'>...</a>
Line 157
<a href='...;' onfocus='blur();'>...</a>
Line 163

https://www.w3.org/WAI/demos/bad/before/tickets.html

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.
<select onchange='location.href = this.value;'>...</select>
Line 189

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<select onchange='location.href = this.value;'>...</select>
Line 188

https://www.w3.org/WAI/demos/bad/before/home.html

<select onchange='location.href = this.value;'>...</select>
Line 89

https://www.w3.org/WAI/demos/bad/before/news.html

<select onchange='location.href = this.value;'>...</select>
Line 84

https://www.w3.org/WAI/demos/bad/before/tickets.html

This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
CriticalSome table header cells have no corresponding data cells. WCAG 2.1 A 1.3.1 Section 508 (2017) A 1.3.1 1 pages
<th align='left' colspan='3'><span>Which is ... park?</span></th>
Line 193

https://www.w3.org/WAI/demos/bad/before/survey.html

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
<a href='../news/annotations' onfocus='blur();'>Man Gets ... Case</a>
Line 283
<a href='../news/annotations' onfocus='blur();'>Lack of ... research</a>
Line 284
<a href='../news/annotations' onfocus='blur();'>Heat wave ...s</a>
Line 282
<a href='../survey/annotations' onfocus='blur();' style='...'>....</a>
Line 341
<a href='../news/annotations' onfocus='blur();'>...</a>
Line 296

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<a href='news.html' onfocus='blur();'>Heat wave linked to temperatures</a>
Line 281
<a href='news.html' onfocus='blur();'>Man Gets Nine Months in Violin Case</a>
Line 282
<a href='news.html' onfocus='blur();'>Lack of brains hinders research</a>
Line 283
<a href='tickets.html' onfocus='blur();' style='...'>Read More...</a>
Line 319
<a href='survey.html' onfocus='blur();' style='...'>Read More...</a>
Line 340

https://www.w3.org/WAI/demos/bad/before/home.html

<a href='...;' onfocus='blur();'>...</a>
Line 150
<a href='...;' onfocus='blur();'>...</a>
Line 156
<a href='...;' onfocus='blur();'>...</a>
Line 162
<a href='...;' onfocus='blur();'>...</a>
Line 168

https://www.w3.org/WAI/demos/bad/before/news.html

<a href='...;' onfocus='blur();'>...</a>
Line 145
<a href='...;' onfocus='blur();'>...</a>
Line 151
<a href='...;' onfocus='blur();'>...</a>
Line 157
<a href='...;' onfocus='blur();'>...</a>
Line 163

https://www.w3.org/WAI/demos/bad/before/tickets.html

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
<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 173
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 182
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 241
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 350
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px'>...</table>
Line 214

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 172
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 181
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 240
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 349
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px'>...</table>
Line 213

https://www.w3.org/WAI/demos/bad/before/home.html

<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 73
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 82
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 141
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 258
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px'>...</table>
Line 114

https://www.w3.org/WAI/demos/bad/before/news.html

<table width='800px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 68
<table width='780px' height='144px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 77
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='white'>...</table>
Line 136
<table width='780px' height='17px' border='0px' cellspacing='0px' cellpadding='0px' bgcolor='#ededed'>...</table>
Line 277
<table width='780px' border='0px' cellspacing='0px' cellpadding='0px'>...</table>
Line 109

https://www.w3.org/WAI/demos/bad/before/tickets.html

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.
<html><head><title>Welcome ... Page]</title><style>...</style>...</head>...</html>
Line 1

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<html><head><title>Welcome ... Page]</title><style>...</style>...</head>...</html>
Line 2

https://www.w3.org/WAI/demos/bad/before/home.html

<html><head><title>Welcome ... Page]</title><style>...</style>...</head>...</html>
Line 1

https://www.w3.org/WAI/demos/bad/before/news.html

<html><head><title>Welcome ... Page]</title><style>...</style>...</head>...</html>
Line 1

https://www.w3.org/WAI/demos/bad/before/tickets.html

This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.

Level AA

1 issues on 4 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 4 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:
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 10.67ptfont-weight: 700
<b>Free Penguins</b>
Line 311
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 10.67ptfont-weight: 700
<b>More City Parks</b>
Line 332

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

The text color to background color contrast ratio after composition is:
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 10.67ptfont-weight: 700
<b>Free Penguins</b>
Line 310
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 10.67ptfont-weight: 700
<b>More City Parks</b>
Line 331

https://www.w3.org/WAI/demos/bad/before/home.html

The text color to background color contrast ratio after composition is:
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 10.67ptfont-weight: 700
<b>[TITLE]</b>
Line 178
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 10.67ptfont-weight: 700
<b>[TITLE]</b>
Line 199

https://www.w3.org/WAI/demos/bad/before/template.html

The text color to background color contrast ratio after composition is:
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 9ptfont-weight: 700
<font color='41545d'>ADULT</font>
Line 207
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 9ptfont-weight: 700
<font color='41545d'>FS</font>
Line 208
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 9ptfont-weight: 700
<font color='41545d'>RS</font>
Line 209
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 9ptfont-weight: 700
<font color='41545d'>DC</font>
Line 210
3.88 with color: rgb(65,84,93)background: rgb(169,184,191)
font-size: 9ptfont-weight: 700
<font color='41545d'>ST</font>
Line 211

https://www.w3.org/WAI/demos/bad/before/tickets.html

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
<a onfocus='blur();' href='../../offsite.html' target='_blank'>Click here</a>
Line 300
<a onfocus='blur();' href='../../offsite.html' target='_blank'>Click here</a>
Line 300

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

<a onfocus='blur();' href='../offsite.html' target='_blank'>Click here</a>
Line 299
<a onfocus='blur();' href='../offsite.html' target='_blank'>Click here</a>
Line 299

https://www.w3.org/WAI/demos/bad/before/home.html

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
<a rel='copyright' href='...t'>Copyright</a>
Line 352
5.83 with color: rgb(34,108,142)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<a href='../survey/annotations' onfocus='blur();' style='...'>Read More...</a>
Line 341
5.83 with color: rgb(34,108,142)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<a href='../tickets/annotations' onfocus='blur();' style='...'>Read More...</a>
Line 320
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='World Wide Web Consortium'>W3C</acronym>
Line 352
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='Massachusetts Institute of Technology'>MIT</acronym>
Line 352

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

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
<a rel='copyright' href='...t'>Copyright</a>
Line 351
5.83 with color: rgb(34,108,142)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<a href='tickets.html' onfocus='blur();' style='...'>Read More...</a>
Line 319
5.83 with color: rgb(34,108,142)background: rgb(255,255,255)
font-size: 12ptfont-weight: 400
<a href='survey.html' onfocus='blur();' style='...'>Read More...</a>
Line 340
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='World Wide Web Consortium'>W3C</acronym>
Line 351
5.83 with color: rgb(34,108,142)background: rgb(255,255,255)
font-size: 11.25ptfont-weight: 400
<a onfocus='blur();' href='../offsite.html' target='_blank'>Click here</a>
Line 299

https://www.w3.org/WAI/demos/bad/before/home.html

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
<a rel='copyright' href='...t'>Copyright</a>
Line 260
6.77 with color: rgb(65,84,93)background: rgb(237,237,237)
font-size: 12ptfont-weight: 400
<font size='3'>Your Shout</font>
Line 196
6.77 with color: rgb(65,84,93)background: rgb(237,237,237)
font-size: 10.67ptfont-weight: 400
<font size='2'>Brain donations at city hospital (by month)</font>
Line 218
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='World Wide Web Consortium'>W3C</acronym>
Line 260
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='Massachusetts Institute of Technology'>MIT</acronym>
Line 260

https://www.w3.org/WAI/demos/bad/before/news.html

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
<a rel='copyright' href='...t'>Copyright</a>
Line 279
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='World Wide Web Consortium'>W3C</acronym>
Line 279
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='Massachusetts Institute of Technology'>MIT</acronym>
Line 279
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<acronym title='European Research Consortium for Informatics and Mathematics'>ERCIM</acronym>
Line 279
4.98 with color: rgb(34,108,142)background: rgb(237,237,237)
font-size: 9ptfont-weight: 400
<a href='http://www.keio.ac.jp/'>Keio</a>
Line 279

https://www.w3.org/WAI/demos/bad/before/tickets.html

This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
ImportantLink uses non-descriptive 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...
<a href='../survey/annotations' onfocus='blur();' style='...'>Read More...</a>
Line 341
Link text: Read More...
<a href='../tickets/annotations' onfocus='blur();' style='...'>Read More...</a>
Line 320
Link text: Click here
<a onfocus='blur();' href='../../offsite.html' target='_blank'>Click here</a>
Line 300
Link text: Click here
<a onfocus='blur();' href='../../offsite.html' target='_blank'>Click here</a>
Line 300

https://www.w3.org/WAI/demos/bad/before/annotated/home.html

Link text: Read More...
<a href='tickets.html' onfocus='blur();' style='...'>Read More...</a>
Line 319
Link text: Read More...
<a href='survey.html' onfocus='blur();' style='...'>Read More...</a>
Line 340
Link text: Click here
<a onfocus='blur();' href='../offsite.html' target='_blank'>Click here</a>
Line 299
Link text: Click here
<a onfocus='blur();' href='../offsite.html' target='_blank'>Click here</a>
Line 299

https://www.w3.org/WAI/demos/bad/before/home.html

Link text: Read more...
<a href='info' onfocus='blur();' style='...'>Read more...</a>
Line 208
Link text: Read more...
<a href='info' onfocus='blur();' style='...'>Read more...</a>
Line 187

https://www.w3.org/WAI/demos/bad/before/template.html

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...Line 319
Link text: Read More...Line 340

https://www.w3.org/WAI/demos/bad/before/home.html

Link text: Home PageLine 63
Link text: Home PageLine 75

https://www.w3.org/WAI/demos/bad/before/reports/home.html

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.html

Line 1

Expand all 18 issues