Accessibility & A11Y support

Ethnio screeners work with all screen readers, assistive devices, and are highly compliant with Section 508 and WCAG 2.0 (Level AA) and the NVDA reader on Windows. Since most content in Ethnio is defined by the customer, including language, colors, and links, the accessibility of any given screener is largely controlled by the customer. For example, make sure to use high contrast colors and clear language for questions and buttons.

Highlights

Every Ethnio screener automatically scales content according to ViewPort size, which means screen readers and large fonts will always function well with Ethnio. The one caveat is that our JavaScript is placed within your site, so we are somewhat limited to the overall accessibility of any page where Ethnio JS code is placed. Here are some highlighted key accessibility features in Ethnio:

• Keyboard support and active state for every input and control. Questions, logos, radio buttons, open fields - respondents can tab through and enter every element without a mouse and assistive devices can complete all fields.
  
• Alt text for every object - there are descriptions for every single selectable object including images
  
• Specific issues to accomodate NVDA. We Use aria-labelledby instead of aria-describedby, role="radiogroup" instead of role="group", and have required attributes for required questions and we hide the necessary required symbols from screen readers to avoid confusion.
  
  

Known Issues

If you run a test of any Ethnio screener link in an accessibility testing tool like WAVE, you'll notice some small errors around structure and formatting that do not impact the vast majority of screen readers and assistive devices. That said, we’re mostly compliant with Section 508 and WCAG 2.0 (Level AA). For example, things like “missing site map” are not relevant to a recruiting screener.

• Loading indicators need alt text. They only display for a millisecond so most respondents will never see them.
• Bold tags instead of strong.