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.
| WCAG2 | Section 508 | Key |
|---|
| A |  | | Priority A - accessibility users will find it impossible to use some pages |
|---|
| AA |
|
|  Priority AA - accessibility users will find it difficult to use some pages |
|---|
| Priority | URL / Description | | Line |
|---|
Priority 1 Issues (Level A) |
| | All ONMOUSEOUT handlers should have an equivalent ONBLUR handler. | Section 508 1194.22 (l) WCAG 2.0 A F54 | |
|
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users. | | |
| http://cook-my-catch.com/ | | 708 |
| | All ONMOUSEOVER handlers should have an equivalent ONFOCUS handler. | Section 508 1194.22 (l) WCAG 2.0 A F54 | |
|
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users. | | |
| http://cook-my-catch.com/ | | 708 |
| | Headings should not contain other headings. | WCAG 2.0 A 1.3.1 | |
|
Remove the nested headings, or replace them with SPAN elements. | | |
| http://cook-my-catch.com/ | | 708 |
| | Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'. | Section 508 1194.22 (g) WCAG 2.0 A F91 | |
|
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. | | |
| http://cook-my-catch.com/ | | 708 |
| | INPUT TYPE=IMAGE tags must have an ALT attribute. | Section 508 1194.22 (a) WCAG 2.0 A F65 | |
|
Add an ALT attribute describing the button action, which screen readers read aloud.
INPUT TYPE=IMAGE elements labelled with the TITLE attribute don't work in:
- SaToGo 3.4 with Internet Explorer 11 (reads title when tabbing, but not when reading)
| | |
| http://cook-my-catch.com/ | | 708 |
| | Provide a way to skip repetitive navigation links. | Section 508 1194.22 (o) | |
|
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
| | |
| http://cook-my-catch.com/ | | 708 |
| | This page has links to a PDF file, but does not provide a link to download Acrobat Reader. | Section 508 1194.22 (m) | |
|
You should include a link to download Acrobat Reader.
When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with S1194.21(a) through (l). | | |
| http://cook-my-catch.com/ | | 708 |
| | This page has markup errors, causing screen readers to miss content. | WCAG 2.0 A F70 | |
|
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content. | | |
| http://cook-my-catch.com/ | | 57 59 109 110 338
...
|
| 8 issues on 1 pages |