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.0 | 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
4 issues on 8 pages | |
| | Identify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'. | WCAG 2.0 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 Safari OSX 10.9 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://nastol.net/ | Line 2 325 | |
| | This form control has no LABEL and no programmatically determined name. | WCAG 2.0 A F68 Section 508 (2017) A F68 | 8 pages |
|
A programmatically determined name allows screen readers to tell the user what the control does. To add a name 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-LABELLEDBY attribute (not supported in all screen readers)
- Add an ARIA-LABEL attribute (not supported in all screen readers)
| | |
| https://nastol.net/ | Line 42 | |
| https://nastol.net/anime/ | Line 42 | |
| https://nastol.net/aviatsiya/ | Line 42 | |
| https://nastol.net/goroda/ | Line 42 | |
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This page uses nested tables, which do not make sense when read in a screen reader. | WCAG 2.0 A F49 Section 508 (2017) A F49 | 1 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. | | |
| https://nastol.net/ | Line 2 | |
| | Use the LANG attribute to identify the language of the page. | WCAG 2.0 A 3.1.1 Section 508 (2017) A 3.1.1 | 8 pages |
|
In HTML add a LANG attribute to the HTML tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly. | | |
| https://nastol.net/ | Line 2 | |
| https://nastol.net/anime/ | Line 2 | |
| https://nastol.net/aviatsiya/ | Line 2 | |
| https://nastol.net/goroda/ | Line 2 | |
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
Level AA
1 issues on 1 pages | |
| | Ensure that foreground and background colors have enough contrast. | WCAG 2.0 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 foreground to background color contrast ratio is: 4 with
color: rgb(255, 255, 255);
background-color: rgb(66, 133, 180);
font-size: 12pt;
font-weight: 400 4 with
color: rgb(255, 255, 255);
background-color: rgb(66, 133, 180);
font-size: 10.5pt;
font-weight: 400 4 with
color: rgb(255, 255, 255);
background-color: rgb(66, 133, 180);
font-size: 12pt;
font-weight: 400
https://nastol.net/ | Line 2 39 40 | |
| Expand all 5 issues | | |