Ember-power-select: a11y: Navigating expanded powerSelect with the keyboard doesn't cause the selected item to be spoken by screen reader.

Created on 28 May 2020 · 3Comments · Source: cibernox/ember-power-select

Steps to reproduce:

With NVDA and Firefox, in the sample app, navigate to the PowerSelect.
Press Space to open.
Once expanded, press up and down arrows.

Expected: NVDA would read the selected item.
Actual: Nothing is spoken. Or NVDA doesn't even switch to focus mode and doesn't recognize that the dropdown opened.

With VoiceOver on the Mac, seeing the same thing. Up and Down don't speak the new value once the dropdown is open.

Source

MarcoZehe

👍3

Most helpful comment

@cibernox there are a couple of blocking a11y issues that prevent us from using this addon at work- this issue is one of them. Would you be open a chat about how we can help these get unblocked?

MelSumner on 21 Jul 2020

👍2

All 3 comments

To be clearer, this component needs to implement the full combobox design pattern from the WAI-ARIA authoring practices. It currently only implements pieces of it and is therefore not fully accessible to users of assistive technologies.

CC @mydea because you previously showed an interest in a11y of this component, and @jayjayjpg because we talked about accessibility in the Ember.js eco system before.

MarcoZehe on 28 May 2020

👍1

@cibernox there are a couple of blocking a11y issues that prevent us from using this addon at work- this issue is one of them. Would you be open a chat about how we can help these get unblocked?

MelSumner on 21 Jul 2020

👍2

a11y should be a top priority. Happy to help with some general guidance.