JedWatson / JedWatson/react-select
A11y issue with searchable select
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
I use NVDA with Chrome for testing
There are two issues
- When I try to search something which is not match any option
For example I try to search "Hello" here https://react-select.com/async (first example)
"No options" will appear and visually it is ok, but Screen Reader say nothing in this case, but it should say "no options" or maybe "number of available results is zero" or something to notify user that there is np results - If I try to search something which match an option with the first letter, for example "O" - SR will say correct number of option, but if then I will continue typing and type "Odg" SR again repeat the previous result which is not correct
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
Start with the first async example on react-select.com/async and reproduce both cases using NVDA with Chrome: a search with no matches and a progressively narrowed search such as “O” then “Odg”. Trace how result announcements are produced, then verify that the spoken result count or no-results message matches the current search.
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