swagger-api
Ensures select element has an accessible name (select)
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
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
Hi @maggiewachs, Is there any update on this bug, and could you please provide a tentative ETA for fixing it?
See my comment here: https://github.com/swagger-api/swagger-ui/issues/8172#issuecomment-2286601376
Hi @ponelat, is there any update on this bug and could you please provide a tentative ETA for fixing it.
@msftedad our implementation also needs these updates, so we've decided to take the initiative to fix them. I don't have a timeline, but the goal is to provide patches back to this repo.
Hi @maggiewachs, this issue is still repro'ing in the latest version of Swagger UI(5.20.1). Could you please confirm if the timeline for fixing it has been finalized? Thanks
CC: @ponelat
@msftedad our timeline isn't immediate, sorry. I recommend following this repository for updates if/when they happen. Or consider fixing the issues yourself? I don't see much movement or involvement from the maintainers anymore.
@maggiewachs Feel free to reach out if I can take on any of the tasks. As long as I've been on GitHub, I really should be contributing more, and addressing some of these would go a long way towards 508 compliance.
