swagger-api / swagger-api/swagger-ui
Ensures select element has an accessible name (select)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Issue:
Ensures select element has an accessible name (select)
User Experience:
User who relies on screen reader is being affected.
Test environment:
OS: Win 11, OS 22000.675
Microsoft Edge Version 102.0.1245.33 (Official build) (64-bit)
AT: Accessibility Insights for Web Version 2.32.0
System Setting:
N/A
Repro Steps:
Hit the URL https://validator.swagger.io/ .
'Home page' screen will open
Start AI4W tool and inspect a screen for any issues.
Actual Result:
Selected element not have accessible name (select)
Expected Result:
Ensures select element has an accessible name (select)
MAS Reference:

[MAS 1.3.1 – Info and Relationships .docx (sharepoint.com)]
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
The issue does not name a source file or test; start by opening the validator.swagger.io home page and inspecting the reported select element with Accessibility Insights for Web. Done means the select has an accessible name and the accessibility check no longer reports this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100