JedWatson / JedWatson/react-select
NVDA screen reader: instructions not read out on first focus
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
When using the freely-available NVDA screen reader, instructions for the select component are not read out until the menu is displayed.
Example responses with v2 sandbox:
- First focus: "edit has auto complete blank"
- Down arrow pressed: "option Yellow focused, 6 of 10. 10 results available. Use Up and Down to choose options, press Backspace to select the currently focused option, press Escape to exit the menu, press Tab to select the option and exit the menu."
- Enter pressed: "10 results available. Select is focused ,type to refine list, press Down to open the menu, "
I would expect "10 results available. Select is focused ,type to refine list, press Down to open the menu" to be read out when the menu is first focused, as well as when an option is chosen.
I'm not sure if this behavior occurs with other screen readers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the select component behavior with NVDA using the linked v2 sandbox, comparing announcements on first focus, after Down, and after Enter. Done means the expected “10 results available...” instruction is announced on initial focus as well as after an option is chosen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100