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 element 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 text is blank, screen readers have nothing to read, so read out the URL instead.
The TITLE attribute on the A element doesn'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)
| | |
| https://brookbend.com/ | | 21 21 31 31 36
...
|
| https://brookbend.com/my-account/?action=login | | 21 21 31 |
| https://brookbend.com/my-account/?action=register | | 21 21 31 |
| https://brookbend.com/product-category/dining-patio/ | | 21 21 31 |
| This issue was found on another 6 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | 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)
| | |
| https://brookbend.com/ | | 21 36 |
| https://brookbend.com/my-account/?action=login | | 21 31 |
| https://brookbend.com/my-account/?action=register | | 21 31 |
| https://brookbend.com/product-category/dining-patio/ | | 21 31 31 |
| This issue was found on another 6 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. | | |
| https://brookbend.com/ | | 21 36 |
| https://brookbend.com/my-account/?action=login | | 21 31 |
| https://brookbend.com/my-account/?action=register | | 21 31 |
| https://brookbend.com/product-category/dining-patio/ | | 21 31 31 |
| This issue was found on another 6 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This link uses general text like "Click Here" and has no surrounding text to make the context clear. | WCAG 2.0 A F63 | |
|
Screen readers read text around links to help understand what the link does. If there's no surrounding text and the link text is very general there's no way to work out what the link does.
Additional link text added with the TITLE attribute doesn't work in:
- NVDA 2014.1 with IE11 (the link title isn't read when tabbing)
- JAWS 14 with IE11 or Firefox 29 (the link title isn't read when tabbing)
- WindowEyes 8.4 with IE11 (the link title isn't read when tabbing)
| | |
| Link text: "Read More"
https://brookbend.com/ | | 32 |
| | This page has duplicate IDs which cause problems in screen readers. | WCAG 2.0 A F77 | |
|
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://brookbend.com/ | | 31 |
| https://brookbend.com/my-account/?action=login | | 31 |
| https://brookbend.com/my-account/?action=register | | 31 |
| https://brookbend.com/product-category/dining-patio/ | | 31 |
| | 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. | | |
| https://brookbend.com/ | | 21 31 |
| https://brookbend.com/my-account/?action=login | | 21 31 |
| https://brookbend.com/my-account/?action=register | | 21 31 |
| https://brookbend.com/product-category/dining-patio/ | | 21 31 |
Priority 2 Issues (Level AA) |
| | Ensure that foreground and background colors have enough contrast. | WCAG 2.0 AA 1.4.3 | |
|
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/background contrast ratio is 2.8
with 7.5 point text.
https://brookbend.com/ | | 21 32 36 36 36 |
| | 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 | |
|
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: "Password *"
https://brookbend.com/my-account/?action=login | | 21 21 31 31 |
| Label used: "Password *"
https://brookbend.com/my-account/?action=register | | 21 21 31 31 |
| | Headings should not be empty. | WCAG 2.0 AA G130 | |
|
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. - SaToGo 3.4.96.0 IE11 Windows 7 Heading: Reads following paragraph as heading.
| | |
| https://brookbend.com/ | | 32 36 |
Priority 3 Issues (Level AAA) |
| | Don't use generic text like "Click Here" or "Read More" in link text, because it says nothing about the link target when read out by a screen reader. | WCAG 2.0 AAA F84 | |
|
Screen readers often tab from one link to the next.
Tabbing between links labelled "click here" sounds like "Click here, tab, click here, tab, click here".
Change the link text to make sense when read without the surrounding text.
Additional link text added with the TITLE attribute doesn't work in:
- NVDA 2014.1 with IE11 (the link title isn't read when tabbing)
- JAWS 14 with IE11 or Firefox 29 (the link title isn't read when tabbing)
- WindowEyes 8.4 with IE11 (the link title isn't read when tabbing)
| | |
| Link text: "Read More"
https://brookbend.com/ | | 32 |
| | Ensure that foreground and background colors have a 7:1 contrast ratio. | WCAG 2.0 AAA 1.4.6 | |
|
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 4.5 or more for 18 point text, or larger
- The contrast ratio should be 4.5 or more for 14 point bold text, or larger
- The contrast ratio should be 7.0 or more for all other text
Note: The default link color in IE11 has poor contrast on a white background. Fix by specifying a:link and a:visited colors in CSS.
| | |
| The foreground/background contrast ratio is 5.7
https://brookbend.com/ | | 36 36 36 36 36
...
|
| 11 issues on 10 pages |