JedWatson / JedWatson/react-select
Aria-autocomplete="list" is getting added even if isSearchable={false} causing Accessibility issue
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
As per my understanding if isSearchable={false} the aria-autocomplete attribute should not be added to the input element as the user won't be able to type anything so that they can have any autocomplete suggestions, I've also tried to remove it using the custom input component prop but it didn't worked for me with isSearchable={false}.
The main issue with this is that the NVDA Speech Viewer is displaying and announcing that the dropdown has auto complete, where as it is not even allowing a user to type or input some text.
Code Sandbox: aria-autocomplete not removing when isSearchable is false
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 linked CodeSandbox and reproduce the rendered input with isSearchable={false}. Inspect how aria-autocomplete is applied and verify the custom input prop behavior. Done means the attribute is absent when searching is disabled while autocomplete remains available for searchable selects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100