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]: In Scan mode, Reading order of Title bar, System Settings, minimize, maximize, and close control is incorrect. #15253

New Issue
Open
opened 2026-01-31 04:32:56 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 04:32:56 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Sep 17, 2021).

Windows Terminal version (or Windows build number)

1.10.2383.0

Other Software

Test Environment:
OS: Windows 11 Version 21H2 (OS Build 22000.168)
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using "Ctrl + ',' ".
  3. Open Narrator using 'Win + Ctrl + Enter' key and ensure Scan mode is ON.(Turn on Scan on mode using 'Caps lock + Space' keys).
  4. Navigate after 'Save' button in scan mode using 'down' arrow key.
  5. Observe the issue.

User Experience:
Screen Reader user will be impacted here if reading order of control is incorrect as result, they will get confused and find difficulty to found them if they are come in expected reading order.

Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence

Attachments:
Reading order of Title bar, System Settings, minimize, maximize, and close control is incorrect when Screen Reader user navigate in scan mode by arrow key as it is coming after last control..zip

Expected Behavior

Title bar, System Settings, minimize, maximize, and close control should come first in reading order when Screen Reader user navigate in scan mode by arrow key.

Actual Behavior

Reading order of Title bar, System Settings, minimize, maximize, and close control is incorrect when Screen Reader user navigate in scan mode by arrow key as it is coming after last control. Same issue repro throughout the app.

Originally created by @ghost on GitHub (Sep 17, 2021). ### Windows Terminal version (or Windows build number) 1.10.2383.0 ### Other Software **Test Environment:** OS: Windows 11 Version 21H2 (OS Build 22000.168) Screen Reader: Narrator Tool: Accessibility Insight for Windows ### Steps to reproduce **Repro Steps:** 1. Open Windows Terminal. 2. Open Settings page using "Ctrl + ',' ". 3. Open Narrator using 'Win + Ctrl + Enter' key and ensure Scan mode is ON.(Turn on Scan on mode using 'Caps lock + Space' keys). 4. Navigate after 'Save' button in scan mode using 'down' arrow key. 5. Observe the issue. **User Experience:** Screen Reader user will be impacted here if reading order of control is incorrect as result, they will get confused and find difficulty to found them if they are come in expected reading order. **Guideline Reference:** https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence **Attachments:** [Reading order of Title bar, System Settings, minimize, maximize, and close control is incorrect when Screen Reader user navigate in scan mode by arrow key as it is coming after last control..zip](https://github.com/microsoft/terminal/files/7185019/Reading.order.of.Title.bar.System.Settings.minimize.maximize.and.close.control.is.incorrect.when.Screen.Reader.user.navigate.in.scan.mode.by.arrow.key.as.it.is.coming.after.last.control.zip) ### Expected Behavior Title bar, System Settings, minimize, maximize, and close control should come first in reading order when Screen Reader user navigate in scan mode by arrow key. ### Actual Behavior Reading order of Title bar, System Settings, minimize, maximize, and close control is incorrect when Screen Reader user navigate in scan mode by arrow key as it is coming after last control. Same issue repro throughout the app.
claunia commented 2026-01-31 04:32:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 18, 2021):

(@v-rpundir I think you forgot to tag this one up 😉)

@zadjii-msft commented on GitHub (Sep 18, 2021): (@v-rpundir I think you forgot to tag this one up 😉)
claunia commented 2026-01-31 04:32:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 2, 2022):

from zip:

https://user-images.githubusercontent.com/18356694/182364121-162daf46-b299-48ab-affd-f6f5edb52e15.MP4

@zadjii-msft commented on GitHub (Aug 2, 2022): from zip: https://user-images.githubusercontent.com/18356694/182364121-162daf46-b299-48ab-affd-f6f5edb52e15.MP4
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 A11ySev3 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Priority-3 Product-Terminal 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#15253
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?