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 - 2000 | 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 4 pages | |
| | Each A element must contain text or an IMG with an ALT attribute. | WCAG 2.0 A F89 Section 508 (2017) A F89 | 1 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.
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)
| | |
| http://velen-spiele.de/ | Line 325 418 | |
| | No TITLE attributes found for the frames on these pages. | Section 508 (2000) 1194.22 (i) WCAG 2.0 A 2.4.1 Section 508 (2017) A 2.4.1 | 1 pages |
|
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://velen-spiele.de/ | Line 302 318 | |
| | This form control has no LABEL and no programmatically determined name. | WCAG 2.0 A F68 Section 508 (2017) A F68 Section 508 (2000) 1194.22 (n) | 4 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)
| | |
| http://velen-spiele.de/ | Line 513 | |
| http://velen-spiele.de/lustige-kinder-und-lernspiele/ | Line 470 | |
| http://velen-spiele.de/shop-spiele/ | Line 495 566 | |
| http://velen-spiele.de/ueber-uns/ | Line 336 | |
| | This form has fields without LABEL elements or TITLE attributes. | Section 508 (2000) 1194.22 (n) | 4 pages |
|
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://velen-spiele.de/ | Line 513 | |
| http://velen-spiele.de/lustige-kinder-und-lernspiele/ | Line 470 | |
| http://velen-spiele.de/shop-spiele/ | Line 495 566 | |
| http://velen-spiele.de/ueber-uns/ | Line 336 | |
| | This page has duplicate IDs which cause problems in screen readers. | WCAG 2.0 A F77 Section 508 (2017) A F77 | 1 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. | | |
| http://velen-spiele.de/shop-spiele/ | Line 642 | |
| | This page has markup errors, causing screen readers to miss content. | WCAG 2.0 A F70 Section 508 (2017) A F70 | 1 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. | | |
| http://velen-spiele.de/shop-spiele/ | Line 642 | |
Level AA
4 issues on 8 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: 3.6 with
color: rgb(102, 102, 102);
background-color: rgba(0, 0, 0, 0.03);
font-size: 10.5pt;
font-weight: 700 1 with
color: rgb(255, 255, 255);
background-color: rgb(255, 255, 255);
font-size: 22.5pt;
font-weight: 700 1 with
color: rgb(255, 255, 255);
background-color: rgb(255, 255, 255);
font-size: 42pt;
font-weight: 400 1 with
color: rgb(255, 255, 255);
background-color: rgb(255, 255, 255);
font-size: 40.5pt;
font-weight: 400
http://velen-spiele.de/ | Line 223 257 265 282 | |
| | 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 | 1 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: Suchen nach: Suchen nach: Suche Suche
http://velen-spiele.de/shop-spiele/ | Line 229 500 631 632 | |
| | This CSS style makes it difficult or impossible to see the dotted link focus outline. | WCAG 2.0 AA F78 Section 508 (2017) AA F78 | 8 pages |
|
Change the style to avoid obscuring the focus outline around A elements, which is used when tabbing through links. Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in: Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls) Firefox (obscures the focus indicator on links) Internet Explorer (obscures the focus indicator on links, buttons and range controls) | | |
| http://velen-spiele.de/ | Line 140 | |
| http://velen-spiele.de/my-account/ | Line 147 | |
| http://velen-spiele.de/shop-spiele/ | Line 140 | |
| http://velen-spiele.de/warenkorb/ | Line 147 | |
| 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 Section 508 (2017) AA 1.4.4 | 8 pages |
|
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, and a lot of people over 50, increase the browser default font size to make text
easier to read. Absolute units ignore this user choice.
Relative units like EM and percentages "stretch" according to the screen size and/or
user's preferred font size, and work on a large range of devices. | | |
| http://velen-spiele.de/ | Line 133 1103 1103 1103 1103
...
| |
| http://velen-spiele.de/my-account/ | Line 140 | |
| http://velen-spiele.de/shop-spiele/ | Line 133 1145 1145 1145 1145
...
| |
| http://velen-spiele.de/warenkorb/ | Line 140 | |
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| Expand all 10 issues | | |