Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide screen reader support for the filters #27

Open
ways2read opened this issue Oct 12, 2018 · 3 comments
Open

Provide screen reader support for the filters #27

ways2read opened this issue Oct 12, 2018 · 3 comments
Assignees

Comments

@ways2read
Copy link
Member

Screen reader experience when setting and changing filters is poor.

System: Windows 10 build 1803, with NVDA and Narrator.

To replicate:
Run an Ace report
Move to the Violations tab and select it
Move further down to Filter by button which should be collapsed. Expand it (with space) and with a screen reader you hear "Expanded".
Tab into the filter boxes and you will hear "Edit".
There are four filter boxes across the screen, these are impact, rule set, rule and location. This text is shown on the screen in each edit box. As you move between the boxes it is not obvious with a screen reader which one you are in. With NVDA it says edit, Narrator is silent.
Alt + down opens a list. With NVDA the list immediately disappears if you try to move down it. With Narrator it behaves better, but the lists are completely silent.
If you manage to add a filter it is added to the edit box, but this is not announced by the screen reader. It is not possible to determine which filters are set.

@marisademeglio
Copy link
Member

Development note: the current filters are created with react-select (https://react-select.com/home)

@rdeltour rdeltour self-assigned this Dec 7, 2018
@marisademeglio
Copy link
Member

There is a chance the component we use will get updated with better a11y support, but it's hard to tell from the issues what the timeline is:
JedWatson/react-select#2456

@nvdaes
Copy link
Contributor

nvdaes commented Aug 4, 2019

Seems edit boxes are not labelled by their corresponding headings. Also, the tooltips read, for example "press arrows to open a menu" (to select an option like moderate and so on, are not localized (always read in English).
While this is nt fixed, baybe useful some kind of documentation explaining that screen readers may prefer to use browser mode (in NVDA), virtual cursor in JAWS, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants