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 Number | Count |
|---|
Level AA
1 issues on 1 pages | |
| If you set any of the colors on the body or a elements you must set all of them. | WCAG 2.1 AA F24 Section 508 (2017) AA F24 | 1 pages |
|
In HTML the color attributes are text, bgcolor, link, alink and vlink.
In CSS the attributes are color and background-color.
Some users have browser defaults set to white text on a black background, so setting
one color without setting the others can result in white text on a white background. | 1.4.3 1.4.6 1.4.8 | |
| The colors used are: | | |
| color: rgb(0,0,0) from browser settings
background: rgb(238,238,238) from www.example.com
<h1>Example Domain</h1>
| Line 11 | |
| color: rgb(0,0,0) from browser settings
background: rgb(238,238,238) from www.example.com
<p>This domain is for use in ... Avoid use in operations.</p>
| Line 13 | |
| https://www.example.com/ | | |
Informative
These messages are for information only and do not indicate errors or conformance problems | |
 | WCAG 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.example.com/ | Line 1 | |
| Expand all 2 issues | | |