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

Screen readers doesn't read elements in expanded list (NVDA and JAWS). #2153

Closed
mpawelski opened this issue Nov 21, 2018 · 6 comments
Closed

Comments

@mpawelski
Copy link

Screen readers doesn't read elements in expanded list (NVDA and JAWS).

Steps to reproduce:

  1. Got to demos page
  2. Run NVDA (to download from here )
  3. Try to focus on first bootstrap select example with keyboard (use Tab and arrows). You will hear something like this when you will try to exand list "mustard button collapsed, expanded, combo box collapsed, list expanded". Now you have expanded list but changing selected list item with arrows or tab key doesn't make it read by screen reader (you have to use mouse to hover over this items to read it).

I was trying to find the solution for it but I'm not that familiar with codebase. It seams that if I remove two roles you set for divs outside of <ul>("combobox" and "listbox") screen reader starts to read this items. But it break "focus trap" on expanded list and seems to break other stuff (list is not always expanded). Small changes I did to investigate it are here

Anyway, that's for working on this library!

@sanjuroo
Copy link

sanjuroo commented Apr 2, 2019

everyone ignore this basic issue?

@caseyjhol
Copy link
Member

@AdrianHostettler
Copy link

Hy, just wanted to let you know, that someone already did some kind of fix for it. Not sure if standards of w3c specs are already met, but it would work for NVDA Screenreader, that's what i tested on v1.13.5.

this is the pull request that solved the issue (but maybe only temporary? the fix worked on v1.13.5.)
#1991

May i ask on which release you are targeting to implement this fix? Already in v1.x.x version, or targeting v2.x.x version?

With kind regards, and thx already for your huge work so far on this library!

@Bene98
Copy link

Bene98 commented Apr 9, 2019

Hey, I had the same problem with chromevox and for me works this solution: #2255

@caseyjhol
Copy link
Member

Hoping to have this available in the next release, as it's a bug.

@caseyjhol
Copy link
Member

Released in v1.13.10!

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

No branches or pull requests

5 participants