Ensures select element has an accessible name (select)

[msftedad]

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:

(https://microsoft.sharepoint.com/:w:/r/sites/accessibility/_layouts/15/Doc.aspx?sourcedoc=%7b97358E88-4367-4121-BF9D-F0C6597D03B7%7d&file=MAS%201.3.1%20%E2%80%93%20Info%20and%20Relationships%20.docx&wdLOR=cC67AE285-FA8E-4A9C-8615-42813289BF4A&action=default&mobileredirect=true&cid=5752710b-7e5b-4fb6-93d5-a98589f9135c)

[MAS 1.3.1 – Info and Relationships .docx (sharepoint.com)]

[mgifford]

This looks like a related issue - #6512 - from AccessibilityInsights.io 

Would also be replicated in axe.

[maggiewachs]

There appear to be a few places where form elements are missing labels, which can be verified with most accessibility browser tools (I used Chrome's WAVE extension) -- see screenshot, which shows a select box and input box with WAVE error/warning badges:

[msftedad]

Hi @maggiewachs, As the verified issue is still reproducible, could you please provide a tentative ETA for fixing it?

[maggiewachs]

@msftedad hello! I wish I had an ETA for you, but I'm not a maintainer and have no idea where these accessibility issues fall in their priority queue. If it were my decision to make, I would rethink this UI rather than make a patchwork of small changes.

I opened a discussion earlier this year to better understand their plans for accessibility updates, feel free to weigh in there? #9702

[msftedad]

@maggiewachs - Thanks for Addressing our remarks for all the bugs, i also found a common bug #7350 created to make Swagger UI accessible. We can wait for next update.

[maggiewachs]

@msftedad this issue (#7350) is over 3 years old and has not been prioritized; the person who opened it disabled their Github account and is no longer tracking it. You may be waiting some time for that update. If you can find out who maintains Swagger UI, tag them in the accessibility tickets you need addressed and see if that creates some movement? At this point my team is exploring alternate tools that provide an accessible experience.

[msftedad]

@maggiewachs - Thanks for this update, will check if we can find any POC for swagger issues.