primefaces / primefaces/primereact
Accessibility issue: Select element must have an accessible name
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 8.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Using a Dropdown without label (the indent feature needed) it's showing critical accessibility issue (Select element must have an accessible name) while accessibility scanning is done. Please find the screenshot attached below.
Reproducer
https://stackblitz.com/edit/e2ccwz8e-5gpz4wkl?file=src%2FApp.jsx
System Information
System:
OS: Windows 11 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
Memory: 368.60 MB / 15.74 GB
Binaries:
Node: 24.5.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 11.5.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Chromium (139.0.3405.102)
Internet Explorer: 11.0.22621.3527
Steps to reproduce the behavior
No response
Expected behavior
No response
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 StackBlitz reproducer and inspect the Dropdown rendering when no label is supplied, confirming the accessibility scanner finding for the generated select. Trace the Dropdown's accessible-name handling and add a regression test for the unlabeled indent case. Done means the scanner no longer reports a missing accessible name while the existing labeled behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100