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

[A11y]Screenreader announce wrong state announced for the radio button Push new packages and package versions as checked. #8495

Closed
ryuyu opened this issue Apr 5, 2021 · 0 comments

Comments

@ryuyu
Copy link
Contributor

ryuyu commented Apr 5, 2021

Link: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1296229

​Environment Details:

Application Name: NuGet Service
#URL: https://www.nuget.org
Operating System: Windows 10
Browser Version: Chrome Version 85.0.4183.121 (Official Build) (64-bit),
Chromium Edge Version 87.0.637.0 (Official build) dev (64-bit)
Screen reader version: JAWS 2020, NVDA 2020.2 .

Repro Steps:​

Hit the URL " https://www.nuget.org" and login with appropriate credentials.
Tab Navigate to "Sign in" control and hit enter.
Tab Navigate to "Sign in with Microsoft" control and hit enter.
Select “API Keys” from the Profile Dropdown and hit enter.
"API Keys" screen gets opened.
Start screenreader and navigate to radio button Push new packages and package versions and observe screenreader announce state as checked.

Actual:​

Screenreader announce wrong state announced for the radio button Push new packages and package versions as checked.

This issue is observed with both JAWS and NVDA.

Expected:​

Screenreader should announce state as selected for the radio button Push new packages and package versions.

​User Impact:​

Screenreader user will not get proper information regarding the state of the controls.

Notes

Looks like some of the controls may be in the wrong order? Unsure of exactly what is causing this one.

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

No branches or pull requests

3 participants