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 | 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
6 issues on 9 pages | |
| Each A element must contain text or an IMG with an ALT attribute. | WCAG 2.0 A F89 Section 508 (2017) A F89 | 9 pages |
|
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead. | | |
| https://www.fieldengineer.com/ | Line 1666 1668 1696 1700 1704
...
| |
| https://www.fieldengineer.com/business/ | Line 895 897 925 929 933
...
| |
| https://www.fieldengineer.com/engineer/ | Line 935 937 965 969 973
...
| |
| https://www.fieldengineer.com/how-it-works/ | Line 938 940 968 972 976
...
| |
| This issue was found on another 5 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| IMG elements must have an ALT attribute. | WCAG 2.0 A F65 Section 508 (2017) A F65 | 1 pages |
|
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''. Impact on users: - 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.
| | |
| https://www.fieldengineer.com/about/ | Line 422 578 711 738 765
...
| |
| Link uses general text like "Click Here" with no surrounding text explaining link purpose. | WCAG 2.0 A F63 Section 508 (2017) A F63 | 1 pages |
|
Screen reader users use text around links to help understand what the link does.
If the link text is very general, and there's no surrounding text, there's no way to work out what the link does.
Either use a descriptive link label (which helps all users) or add an aria-label to the link (which helps screen reader users). | | |
| Link text: Read More Read More Read More Read More Read More https://www.fieldengineer.com/blogs/ | Line 484 586 688 790 892
...
| |
| This form control has no LABEL and no programmatically determined name. | WCAG 2.0 A F68 Section 508 (2017) A F68 | 1 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://www.fieldengineer.com/contact/ | Line 432 437 444 449 491
...
| |
| This page has duplicate IDs which cause problems in screen readers. | WCAG 2.0 A F77 Section 508 (2017) A F77 | 4 pages |
|
Two or more elements on this page share the same ID, which cause problems in screen readers which use IDs for labeling controls and table headings.
This also causes problems in JavaScript methods like getElementById and querySelector, which behave inconsistently when duplicate IDs are present.
Change the ID so it is unique for each element. | | |
| https://www.fieldengineer.com/ | Line 800 | |
| https://www.fieldengineer.com/business/ | Line 764 | |
| https://www.fieldengineer.com/engineer/ | Line 804 | |
| https://www.fieldengineer.com/how-it-works/ | Line 807 | |
| This page has markup errors, causing screen readers to miss content. | WCAG 2.0 A F70 Section 508 (2017) A F70 | 6 pages |
|
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content. | | |
| https://www.fieldengineer.com/ | Line 800 1730 | |
| https://www.fieldengineer.com/business/ | Line 764 959 | |
| https://www.fieldengineer.com/engineer/ | Line 804 999 | |
| https://www.fieldengineer.com/how-it-works/ | Line 807 1002 | |
| This issue was found on another 2 pages.
The trial version is limited to showing issues on 4 pages.
| | |
Level AA
3 issues on 4 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: 2.7 with
color: rgb(255, 255, 255);
background-color: rgb(0, 168, 225);
font-size: 15pt;
font-weight: 700 2.7 with
color: rgb(255, 255, 255);
background-color: rgb(0, 168, 225);
font-size: 15pt;
font-weight: 700 2.3 with
color: rgb(167, 169, 172);
background-color: rgb(255, 255, 255);
font-size: 12pt;
font-weight: 400 2.3 with
color: rgb(167, 169, 172);
background-color: rgb(255, 255, 255);
font-size: 12pt;
font-weight: 400 2.3 with
color: rgb(167, 169, 172);
background-color: rgb(255, 255, 255);
font-size: 12pt;
font-weight: 400 https://www.fieldengineer.com/ | Line 749 765 840 864 886
...
| |
| Form field labels should be unique on a page, or enclosed in a FIELDSET with a LEGEND that makes the label unique. | WCAG 2.0 AA 2.4.6 Section 508 (2017) AA 2.4.6 | 2 pages |
|
When a form contains items with the same label, screen reader users find it difficult to tell them apart.
Adding a fieldset with a legend differentiates the controls, because the legend text is announced along
with the label text. For example:
<legend> Gift wrapped: </legend>
<label> Yes </label>
<label> No </label>
<legend> Express delivery: </legend>
<label> Yes </label>
<label> No </label>
| | |
| Label used: Search for: Search Search for: Search Search for: https://www.fieldengineer.com/blogs/ | Line 6869 6871 7675 7677 8072
...
| |
| Label used: Send Send https://www.fieldengineer.com/contact/ | Line 454 513 | |
| Headings should not be empty. | WCAG 2.0 AA G130 Section 508 (2017) AA G130 | 1 pages |
|
Add text to the heading, or ALT text if the heading contains an image. Screen readers read out page headings, allowing users to quickly skip to a section, but some older screen readers do not ignore empty headings. Impact on users: - SaToGo 3.4.96.0 IE11 Windows 7 Heading: Reads following paragraph as heading.
| | |
| https://www.fieldengineer.com/about/ | Line 389 | |
| Expand all 9 issues | | |