[Power Toys-Genera]: Keyboard focus gets lost after pressing tab and after pressing tab twice it lands on the expected control. #32222
Labels
A11yE+D
Accessibility Team tag- issues found by Accessibility E+D team at Microsoft
A11ySev3
Accessibility team tag - P3 items
A11yWCAG
Accessibility Team tag - Web Content Accessibility Guidelines
Area-Accessibility
Issues related to accessibility
External Dependency-WinUI 3
Dependency on WinUI
Issue-Bug
Something isn't working
Product-Settings
The standalone PowerToys Settings application
Resolution-External
External issue, unrelated to PowerToys
Status-Blocked
We can't make progress due to a dependency or issue
Milestone
Microsoft PowerToys version
v0.79.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
General
Steps to reproduce
Test environment:
OS Build: Windows 11 Enterprise insider preview 23H2 (22631.3296)
Power toys version: v0.79.0
Repro Steps:
User Experience:
Users who rely on keyboard navigation may find it inconvenient and confusing when the keyboard focus is lost unexpectedly. This behavior interrupts the flow of navigation and requires users to press the tab key multiple times to reach the desired control.
Guideline reference:
https://www.w3.org/WAI/WCAG22/Understanding/focus-order
Attachments:
MAS2.4.3_Keyboard.focus.gets.lost.after.pressing.tab.and.after.pressing.tab.twice.it.lands.on.the.expected.control.mp4
✔️ Expected Behavior
When navigating through the editor using keyboard focus, pressing the tab key should move the focus sequentially to each interactive element. After pressing the tab key once, the focus should move to the next interactive element, and after pressing it again, the focus should land on the expected control, such as the Running as user list item.
❌ Actual Behavior
Currently, when navigating through the editor using keyboard focus and pressing the tab key, the focus is lost after the first tab press. After pressing the tab key again, the focus eventually lands on the expected control.
Other Software
No response
The text was updated successfully, but these errors were encountered: