[Skip navigation links]

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.

LevelWCAG 2.1Section 508 - 2017Key
ALevel A, 6 issuesLevel A, 6 issuesCritical Pages with level A issues are unusable for some people
AALevel AA, 1 issuesLevel AA, 1 issuesVery Important Pages with level AA issues are very difficult to use
AAALess Important Pages with level AAA issues can be difficult to use
PriorityDescription and URLGuideline and Line#Count

Level A

6 issues on 2 pages

CriticalAll onclick handlers should have an equivalent onkeyup or onkeydown handler. WCAG 2.1 A F54 Section 508 (2017) A F54 2 pages
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
https://xn--u8ji8cwimisenhof.com/Line 1466
https://xn--u8ji8cwimisenhof.com/article/international-free-call.htmlLine 2631
CriticalClickable controls should be keyboard accessible. WCAG 2.1 A F15 Section 508 (2017) A F15 1 pages
Add tabindex=0 to allow keyboard users to tab to the control.
https://xn--u8ji8cwimisenhof.com/Line 1078
CriticalClickable controls should have an ARIA role. WCAG 2.1 A F54 Section 508 (2017) A F54 1 pages
Controls that respond to clicks should be given an ARIA role such as role=button or role=link.
https://xn--u8ji8cwimisenhof.com/Line 1078
CriticalContent inserted with CSS is not read by some screen readers, and not available to people who turn off style sheets. WCAG 2.1 A F87 Section 508 (2017) A F87 2 pages
Move the content from CSS to the HTML page so that all users can see it.

Impact on users:

  • NVDA 2019.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • NVDA 2018.4 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • NVDA 2017.3 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • NVDA 2016.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • JAWS 2019.1912.1 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • JAWS 2018.1811.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • JAWS 18.0.5038 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
  • JAWS 17.0.2619 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
https://xn--u8ji8cwimisenhof.com/Line 76
https://xn--u8ji8cwimisenhof.com/article/international-free-call.htmlLine 122 172 252 276
CriticalEach a element must contain text or an img with an alt attribute. WCAG 2.1 A F89 Section 508 (2017) A F89 2 pages

A link name allows screen readers to voice what the links does. If there is no link text or the `alt` text is blank, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following:

  • Add text between the a element start and end tags
  • Add an aria-label attribute
  • Add an aria-labelledby attribute
  • Add an img alt attribute if the link contains an img element
https://xn--u8ji8cwimisenhof.com/Line 438
https://xn--u8ji8cwimisenhof.com/article/international-free-call.htmlLine 975
CriticalThe label element is blank. WCAG 2.1 A 4.1.2 Section 508 (2017) A 4.1.2 1 pages
Add text to the label describing the associated control.
https://xn--u8ji8cwimisenhof.com/article/international-free-call.htmlLine 2020 2023 2087 2119 2122

Level AA

1 issues on 2 pages

Very ImportantThe CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. WCAG 2.1 AA F78 Section 508 (2017) AA F78 2 pages
Change the style to avoid obscuring the focus outline around focusable elements.

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)
Internet Explorer does not support the `outline-offset:` property, so using this does not reliably avoid focus outline overlap.
https://xn--u8ji8cwimisenhof.com/Line 76
https://xn--u8ji8cwimisenhof.com/article/international-free-call.htmlLine 252
Expand all 7 issues