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

[BUG] Accessibility issue where screen-readers can only see 'blank' #186

Closed
TroyHouston opened this issue Nov 20, 2019 · 2 comments · Fixed by #190
Closed

[BUG] Accessibility issue where screen-readers can only see 'blank' #186

TroyHouston opened this issue Nov 20, 2019 · 2 comments · Fixed by #190
Labels
bug Something isn't working

Comments

@TroyHouston
Copy link

TroyHouston commented Nov 20, 2019

If you use a screenreader (I am using NVDA) and try to navigate the dropdown using the keyboard it will always read out 'blank' for each item (or the value entered into the search field).

However if the dropdown is not opened then it does read out the value properly.

See both scenarios in action below

To Reproduce

  1. Install NVDA
  2. Go to the demo site
  3. Open NVDA
  4. Tab to the selector
  5. Press spacebar to open the dropdown
  6. Use the arrow keys to navigate the dropdown, each option will be read as 'blank' (or the value entered into the search field)

Expected behavior
I would expect the screen-reader to be able to navigate and read out all the options in the list whether the dropdown is open or closed.

Example Gif
SelectSearchA11y

Desktop

  • OS: Windows 10
  • Browser: Chromium Edge (Also found in other browsers)
  • Version: 80.0.334.2
@TroyHouston TroyHouston added the bug Something isn't working label Nov 20, 2019
@macjohnny
Copy link
Member

@TroyHouston thanks for reporting this issue. I think the problem is that the input field is focused.
Would you like to try and find a solution to tell the screen reader to e.g. read the entered search value and the currently highlighted select value?

@macjohnny
Copy link
Member

@ZacaryPaynter thanks for the fix, it was released with version 2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants