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

While navigating with tab key focus is not going to "Failure description" via keyboard #7218

Open
DaveTryon opened this issue Jan 24, 2024 · 1 comment
Assignees
Labels
bug Something isn't working status: new This issue is new and requires triage by DRI.

Comments

@DaveTryon
Copy link
Contributor

DaveTryon commented Jan 24, 2024

Copied from https://mseng.visualstudio.com/DefaultCollection/1ES/_workitems/edit/2129324

Environment Details:

Application Name: Accessibility Insights for Web
Operating System: Windows 11 Enterprise Insider Preview(23H2)
OS Build: 26010.1000
Edge Version: Version 121.0.2256.2 (Official build) stable app, dev channel (64-bit)

Repro Steps:

  1. Hit the URL https://accessibilityinsights.io, install and add application to edge/ chrome
  2. Tab till Accessibility Insights for web icon and press enter
  3. Tab till ok button in Telemetry and press enter
  4. Tab till Fastpass dropdown and select Assessment link and press enter
  5. Select the keyboard test in the navigation pane and press enter
  6. Select any requirement under this test
  7. Tab till Fail radio button and select it
  8. Tab to failure Description

Observe While navigating with tab key focus is not going to "Failure description" via keyboard

Actual:

While navigating with tab key focus is not going to "Failure description" via keyboard focus is going to direct no keyboard trap button.

Expected:

While navigating with tab key focus should go to "Failure description" and then it should go to no keyboard trap button via keyboard

User Impact:

Keyboard users will face difficulty when focus is not going to "Failure description"

Tasks

No tasks being tracked yet.
@DaveTryon DaveTryon added the bug Something isn't working label Jan 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the status: new This issue is new and requires triage by DRI. label Jan 24, 2024
@DaveTryon
Copy link
Contributor Author

We've confirmed this behavior. The new instance doesn't immediately get added to the tab order. Interestingly, if you tab past the end of the page and back around, it is then in the tab order.

@JGibson2019 JGibson2019 moved this from Needs triage to Accepted - vendor in Accessibility Insights Jan 29, 2024
@rohittarpara rohittarpara self-assigned this Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status: new This issue is new and requires triage by DRI.
Projects
Status: Accepted - vendor
Development

No branches or pull requests

2 participants