NVDA has issues reading options

[kylehalleman]

NVDA can read options very oddly, even breaking apart words or omitting parts of words altogether. Using the first example on the homepage ("Single"), here is the NVDA / Firefox output from initial focus through using ↓ to navigate through the list. Note issue #1585 is still present in this readout.

blank
blank
option Ocean focused, 1 of 10. 10 results available. Use Up and Down to choose options, press Enter to select the currently focused option, press Escape to exit the menu, press Tab to select the option and exit the menu.
blank
Blue focused disabled, 2 of 10. 10 results available. Use Up and Down to choose options
blank
Purple focused, 3 of 10. 10 results available. Use Up and Down to choose options, press Enter to select the currently focused option
blank
Red
4
blank
Orange
5
blank
Yellow
6
blank
Green
7
blank
Fo
st
8
blank
Slate
9
blank
i
ver
10

VoiceOver / Safari reads this sequence as expected.

edit: This comment in a related issue describes what could be the issue and the fix.

[agonzalezcr]

did you find a work around for this @kylehalleman ?

[kylehalleman]

@agonzalezcr Unfortunately no. I did try shortly after filing this issue to fix it in the library to eventually make a PR. Didn't get too far though.

[ebonow]

Greetings @agonzalezcr and @kylehalleman ,

I am working on a fairly large PR to address many of the accessibility and aria-live issues.

It would be appreciated if someone could test these changes against JAWS or NVDA as all of my testing has been against OSX VoiceOver.

PR with description: #4414
Git branch: https://github.com/ebonow/react-select/tree/aria-messages-v4

[kylehalleman]

Unfortunately I've changed jobs since I created this issue and no longer have access to NVDA to be able to test this. I'll see if there's some way I can get a setup going to test this and get back to you.

[ebonow]

@kylehalleman thank you and no pressure. Jed has mentioned that there will be another internal member added to the team soon that will be focusing on accessibility, but again just happy to address any issues and welcome any assistance the community is able to provide.

[mellis481]

@ebonow Your work in #4414 did not address the "blank" problem reported in this issue and others. Is there any update?

[SairamAlagapan]

Any update on this please?