JedWatson / JedWatson/react-select

AsyncSelect doesn't announce 'No Options' message

Open
#5,510 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

issue/bug-unconfirmed
Dominant language
TypeScript
Stars
28k
Forks
4.1k
PR merge metrics
No merged PRs in 30d

Description

In AsyncSelect 'No options' message is not announced by NVDA, this might confuse user that after typing in no any feedback is get:
Screenshot 2022-12-09 at 17 31 09

In syncronious Select NVDA reads out '0 results available for search' when 'no optoins' gets back on search.
Screenshot 2022-12-09 at 17 30 04

Need to provide AsyncSelect with feedback when search returns no results.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the AsyncSelect implementation and compare its no-results announcement with the synchronous Select behavior described in the issue. Reproduce an empty search with NVDA, then verify that AsyncSelect provides equivalent feedback when the search returns no results.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.