starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Settings]: Incorrect keyboard focus is observed when naviagting under 'Color' pop-up. #20493

New Issue
Open
opened 2026-01-31 07:15:27 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:15:27 +00:00
Owner
Copy Link

Originally created by @Priyanka-Chauhan123 on GitHub (Sep 18, 2023).

Windows Terminal version

1.19.2481.0

Windows build number

23529.1000

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 23529.1000)
App: Windows Terminal Preview

Steps to reproduce

**Repro Steps: **

1.Open Windows Terminal.
2.Open Settings page using 'Ctr+,'
3. Set shortcut for 'Set tab color'.
4. Now navigate back to the Window terminal page and Open color pop-up using shortcut.
5. Navigate over the controls and observe the issue.

**User Experience: **
Users who rely on keyboard expect a sequential focus order that is top to down and left to right, if that is not followed then users might get confused and can miss the control.

MAS Reference:
https://www.w3.org/WAI/WCAG21/Understanding/focus-order

Attachment:
Incorrect keyboard focus is observed when naviagting under 'Color' pop-up..zip

Expected Behavior

Correct keyboard focus should be there when navigating under 'Color' pop-up. Focus order should follow left to right and top to down approach.

Actual Behavior

Incorrect keyboard focus is observed when navigating under 'Color' pop-up.

Originally created by @Priyanka-Chauhan123 on GitHub (Sep 18, 2023). ### Windows Terminal version 1.19.2481.0 ### Windows build number 23529.1000 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 23529.1000) App: Windows Terminal Preview ### Steps to reproduce **Repro Steps: ** 1.Open Windows Terminal. 2.Open Settings page using 'Ctr+,' 3. Set shortcut for 'Set tab color'. 4. Now navigate back to the Window terminal page and Open color pop-up using shortcut. 5. Navigate over the controls and observe the issue. **User Experience: ** Users who rely on keyboard expect a sequential focus order that is top to down and left to right, if that is not followed then users might get confused and can miss the control. MAS Reference: https://www.w3.org/WAI/WCAG21/Understanding/focus-order **Attachment:** [Incorrect keyboard focus is observed when naviagting under 'Color' pop-up..zip](https://github.com/microsoft/terminal/files/12644604/Incorrect.keyboard.focus.is.observed.when.naviagting.under.Color.pop-up.zip) ### Expected Behavior Correct keyboard focus should be there when navigating under 'Color' pop-up. Focus order should follow left to right and top to down approach. ### Actual Behavior Incorrect keyboard focus is observed when navigating under 'Color' pop-up.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label A11yCO A11ySev2 A11yWCAG Area-Accessibility Disability-All HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Triage Product-Terminal Resolution-External WindowsTerminal_Win32
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20493
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?