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 | 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 |
|---|
| AAA | | |  Priority AAA - accessibility users will find it somewhat difficult to use some pages |
|---|
| Priority | URL / Description | | Line |
|---|
Priority 1 Issues (Level A) |
| | Each A tag must contain text or an IMG with an ALT attribute. | WCAG 2.0 A F89 | |
|
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT tag is blank, screen readers have nothing to read, so read out the URL instead.
Link A elements labelled with a TITLE attribute, and only containing an image don't work in:
- WindowEyes 8.4 with IE11 (the link HREF is read instead)
- VoiceOver on OSX 10.9 (the image filename is read instead)
| | |
| http://nsgllc.net/dev/about-nsg/certifications-documents/ | | 349 539 636 |
| http://nsgllc.net/dev/about-nsg/our-story/ | | 356 569 |
| http://nsgllc.net/dev/our-team/ | | 351 527 |
| http://nsgllc.net/dev/principles/ | | 355 554 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | IMG tags must have an ALT attribute. | Section 508 1194.22 (a) WCAG 2.0 A F65 | |
|
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''. - NVDA 2015.2 FF40 Windows 7 Reading: Image ignored.
- JAWS 16.0.4350 FF40 Windows 7 Reading: Image ignored.
- WindowEyes 8.4 IE11 Windows 7 Reading: Image ignored.
- VoiceOver Safari OSX 10.10 Reading: Image filename read out.
- VoiceOver Safari iOS 7.1 Touch: Image filename read out.
- SaToGo 3.4.96.0 IE11 Windows 7 Reading: Image ignored.
| | |
| http://nsgllc.net/dev/about-nsg/certifications-documents/ | | 544 545 546 547 550
...
|
| http://nsgllc.net/dev/about-nsg/our-story/ | | 478 495 |
| | No TITLE attributes found for the frames on these pages. | Section 508 1194.22 (i) WCAG 2.0 A 2.4.1 | |
|
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Without a TITLE some screen readers read out the FRAME filename, which is usually meaningless.
IFRAMEs with no title cause problems in:
- JAWS 14 and 15 with Firefox (the frame SRC filename is read instead)
- VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
| | |
| http://nsgllc.net/dev/about-nsg/our-story/ | | 505 |
| | This form control has no programmatically determined name. | WCAG 2.0 A F68 Section 508 1194.22 (n) | |
|
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)
| | |
| http://nsgllc.net/dev/about-nsg/certifications-documents/ | | 352 421 |
| http://nsgllc.net/dev/about-nsg/our-story/ | | 359 428 |
| http://nsgllc.net/dev/our-team/ | | 354 423 |
| http://nsgllc.net/dev/principles/ | | 358 427 476 476 476 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This form has fields without LABEL elements or TITLE attributes. | Section 508 1194.22 (n) | |
|
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | | |
| http://nsgllc.net/dev/about-nsg/certifications-documents/ | | 352 421 |
| http://nsgllc.net/dev/about-nsg/our-story/ | | 359 428 |
| http://nsgllc.net/dev/our-team/ | | 354 423 |
| http://nsgllc.net/dev/principles/ | | 358 427 476 476 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | 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://nsgllc.net/dev/about-nsg/certifications-documents/ | | 499 500 502 503 505
...
|
| | 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://nsgllc.net/dev/about-nsg/certifications-documents/ | | 721 |
| http://nsgllc.net/dev/our-team/ | | 441 |
| http://nsgllc.net/dev/principles/ | | 639 |
| http://nsgllc.net/dev/solutions/ | | 620 |
| | Using the same ALT text on adjacent images results in screen readers stuttering as the same text is read out twice. | WCAG 2.0 A 1.1.1 | |
|
Use ALT='' for the subsequent adjacent images, or change the redundant ALT text. | | |
| http://nsgllc.net/dev/about-nsg/certifications-documents/ | | 370 373 375 |
| http://nsgllc.net/dev/about-nsg/our-story/ | | 377 380 382 |
| http://nsgllc.net/dev/our-team/ | | 372 375 377 |
| http://nsgllc.net/dev/principles/ | | 376 379 381 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
Priority 2 Issues (Level AA) |
| | If you set any of the colors on the BODY or A elements you must set all of them. | WCAG 2.0 AA F24 | |
|
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 black text on a black background. | | |
| http://nsgllc.net/dev/ | | 106 106 |
| http://nsgllc.net/dev/about-nsg/our-story/ | | 107 107 |
| http://nsgllc.net/dev/our-team/ | | 107 107 |
| http://nsgllc.net/dev/principles/ | | 107 107 |
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | Use relative rather than absolute units in CSS property values. | WCAG 2.0 AA 1.4.4 | |
|
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit,
because it isn't relative the user's preferred font size.
Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual.
This usually causes problems with pixel based layouts, which also perform badly on handheld
and widescreen displays. Percentage values "stretch" according to screen size and work on a large
range of display sizes. | | |
| http://nsgllc.net/dev/ | | 106 106 106 106 106
...
|
| http://nsgllc.net/dev/about-nsg/our-story/ | | 107 107 107 107 107
...
|
| http://nsgllc.net/dev/our-team/ | | 107 107 107 107 107
...
|
| http://nsgllc.net/dev/principles/ | | 107 107 107 107 107
...
|
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| 10 issues on 8 pages |