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

[Power Rename]: Focus is not visible after 'use Boost Library' Toggle button #13462

Closed
1 task
DhananjaySaini007 opened this issue Sep 27, 2021 · 1 comment
Closed
1 task
Assignees
Labels
A11yE+D Accessibility Team tag- issues found by Accessibility E+D team at Microsoft A11ySev3 Accessibility team tag - P3 items A11yTTValidated Accessability team tag A11yWCAG Accessibility Team tag - Web Content Accessibility Guidelines Issue-Bug Something isn't working Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@DhananjaySaini007
Copy link

Microsoft PowerToys version

0.45.0

Running as admin

  • Yes

Area(s) with issue?

PowerRename

Steps to reproduce

Steps to reproduce

Test Environment:
OS: Windows 10 Version Dev (Build 22458.1000)
App version: 0.45.0
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

Repro Steps:

  1. Launch 'PowerToys' application.
  2. Navigate to 'PowerRename' and activate it.
  3. Navigate to ' Use Boost Library" toggle using Keyboard tab Navigation.
  4. Now, Press tab key and Observe the Keyboard focus.

Note:
Same issue repro on "Learn more about Power Rename" Link.
Same issue repro on "Power Run" page.

User Impact:
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Guidelines Reference:
https://www.w3.org/TR/WCAG21/#focus-visible

Attachments

Powertoys.-.Focus.not.visible.after.Boost.library.toggle.button.mp4

✔️ Expected Behavior

There should be no focus loss after "Use Boost Library". Focus should always be visible.

❌ Actual Behavior

The focus is lost after "Use Boost Library" on Keyboard tab Navigation

Other Software

No response

@DhananjaySaini007 DhananjaySaini007 added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Sep 27, 2021
@Priyanshu073 Priyanshu073 added A11ySev3 Accessibility team tag - P3 items A11yWCAG Accessibility Team tag - Web Content Accessibility Guidelines A11yE+D Accessibility Team tag- issues found by Accessibility E+D team at Microsoft labels Sep 27, 2021
@niels9001 niels9001 removed the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Sep 27, 2021
@niels9001 niels9001 self-assigned this Sep 27, 2021
@niels9001 niels9001 added the Status-In progress This issue or work-item is under development label Sep 30, 2021
@niels9001 niels9001 mentioned this issue Sep 30, 2021
10 tasks
@niels9001 niels9001 added Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release. and removed Status-In progress This issue or work-item is under development labels Oct 1, 2021
@dedavis6797
Copy link
Contributor

Resolved with v0.49.0. Thanks @niels9001!

@Priyanshu073 Priyanshu073 added the A11yTTValidated Accessability team tag label Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A11yE+D Accessibility Team tag- issues found by Accessibility E+D team at Microsoft A11ySev3 Accessibility team tag - P3 items A11yTTValidated Accessability team tag A11yWCAG Accessibility Team tag - Web Content Accessibility Guidelines Issue-Bug Something isn't working Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

No branches or pull requests

4 participants