Ethnio Accessibility Statement & A11Y support

At Ethnio, we are devoted to fostering more inclusive and accessible interactions for our customers, users, and participants. 

We hold the conviction that nurturing empathy through diverse perspectives is pivotal in crafting outstanding digital experiences for all. This conviction, coupled with our fundamental values of continuous improvement, prioritizing our customers, and treating one another with respect, propels us to deliver accessible experiences.

All Ethnio links, pages, and screeners work with all screen readers, assistive devices, and are highly compliant with  Section 508 and WCAG 2.0 (Level AA) and the NVDA screen readers 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:

• Key places in Ethnio where customers can edit color contrast have built-in automatic accessibility suggestions:
• Focus states and keyboard support for every input and control —including, questions, logos, radio buttons, and open fields. Respondents can tab through and enter every element without a mouse, and assistive devices can complete all fields.
  
• Alt text and descriptions for every single selectable object, including images.
  You can edit the alt text for your company logo / name on all screener pages. This is editable from Screeners >> Design. 

• Specific issues to accommodate NVDA. We Use aria-labelledby instead of aria-describedby, role="radiogroup" instead of role="group", and have required attributes for required questions. We also hide the necessary required symbols from screen readers to avoid confusion.
• Asterisk is a character, not an image.

• Bold text is an issue around strong/bold div tags on any form, not specific to Ethnio. 
• Sample phone number in phone number field has been removed. 

Ethnio also has an established process to review and test accessibility in the product development phase, which is tracked and recorded.

Full control over accessibility by customers 

Each participant-facing component of Ethnio can be adjusted by customers to comply with accessibility guidelines. For example, when creating buttons in Pool (Enterprise-only), the sidebar gives automatic feedback on compliance with color contrast ratios:

Intercepts

Ethnio intercepts allow users to tab through to select options and buttons, along with alt text.Additionally, if you go to Screeners>>Design under "2. Position Your Intercept" there is an option to have the browser pull focus to the intercept.

Incentives & Redeem Links

All redeem links in Ethnio and payment method providers are highly accessible and work with assistive devices, but of course we can only control the redeem links in our system. Note each state and option can be tabbed and selected, with proper identification of all elements:

Sub-methods

After certain payment methods are selected, such as charities or eGift cards, assistive devices should also be able to navigate through subsequent cards using the voice-over equivalent of radio button navigation (arrows or tab on keyboards):

Information link tabbable / compatible with assistive devices:

Success state:

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. ]