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
Environment (OS, Application):
Windows OS version: 21H2 (10.0.19044 Build 19044)Edge
Dev Version : Version 98.0.1108.50 (Official build) (64-bit)
URL: https://wsd-branchmanagement.trafficmanager.net/swagger/index.html
Repro Steps:
- Open https://wsd-branchmanagement.trafficmanager.net/swagger/index.html
- Navigate to [POST] /v2.0/branch/ubr/increment/ and activate it.
- Check the name property of Swagger UI control under the description.
Actual Results
Swagger UI control “.parameters-col_description > select” doesn’t have name
Expected Results
The select name component should have a label and Big Ben -Swagger API page should have zero FastPass bug instances.
Element path
.parameters-col_description > select
Snippet
--truefalse
How to fix
Fix any of the following:
- Form element does not have an implicit (wrapped)
- Form element does not have an explicit
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
- Element's default semantics were not overridden with role="none" or role="presentation"
screenshot

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 Swagger UI control matching .parameters-col_description > select on the documented POST endpoint and compare its accessible name with the expected label behavior. Confirm the fix against the provided reproduction page and verify that the select receives an accessible name without introducing new accessibility violations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100