Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensures select element has an accessible name (select) #8092

Open
msftedad opened this issue Jul 11, 2022 · 4 comments
Open

Ensures select element has an accessible name (select) #8092

msftedad opened this issue Jul 11, 2022 · 4 comments

Comments

@msftedad
Copy link

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:

  1. Open https://wsd-branchmanagement.trafficmanager.net/swagger/index.html
  2. Navigate to [POST] /v2.0/branch/ubr/increment/ and activate it.
  3. 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
image

@msftedad
Copy link
Author

Hi Team, is there any update on this bug?

@msftedad
Copy link
Author

Hi Team,

Any update on this issue?

@msftedad
Copy link
Author

msftedad commented Aug 13, 2024

Hi @maggiewachs, Is there any update on this bug, and could you please provide a tentative ETA for fixing it?

@maggiewachs
Copy link
Contributor

See my comment here: #8172 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants