starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Windows Terminal]: Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode. #22245

New Issue
Closed
opened 2026-01-31 08:07:35 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:07:35 +00:00
Owner
Copy Link

Originally created by @Saurabh220304 on GitHub (Sep 10, 2024).

Windows Terminal version

1.22.2362.0

Windows build number

27695.1000

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 27695.1000)
App: Windows Terminal Preview
Screen Reader: Narrator

Steps to reproduce

Repro steps :
1.Open Windows Terminal.
2.Navigate to the editor.
3.Turn on Narrator by pressing 'Ctrl + Windows + Enter' keys.
4.Now turn on mark mode by pressing 'Ctrl + Shift + M' keys.
5. Now navigate among words using 'Ctrl + Left/Right' keys.
6.Observe the screen reader narration here.

Observation using NVDA and JAWS screen reader:
Same issue repro with NVDA and JAWS screen reader also.

User Experience
Users who rely on screen reader may not get the info properly while navigating in mark mode.

WCAG Reference Link:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

Attachment :
Screen reader is not announcing full word information while navigating via ctrl + left_right arrow keys.zip

Expected Behavior

Screen reader should narrate complete word information while navigating using ctrl + left/right arrow keys in mark mode.

Actual Behavior

Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode.
For example:
For word "Microsoft", screen reader is just announcing as 'M selected' when we navigate using 'Ctrl + Left' arrow key and announces as 't selected' using 'Ctrl + Right' arrow.

Originally created by @Saurabh220304 on GitHub (Sep 10, 2024). ### Windows Terminal version 1.22.2362.0 ### Windows build number 27695.1000 ### Other Software Test Environment: OS: Windows 11 Version Dev (OS Build 27695.1000) App: Windows Terminal Preview Screen Reader: Narrator ### Steps to reproduce **Repro steps :** 1.Open Windows Terminal. 2.Navigate to the editor. 3.Turn on Narrator by pressing 'Ctrl + Windows + Enter' keys. 4.Now turn on mark mode by pressing 'Ctrl + Shift + M' keys. 5. Now navigate among words using 'Ctrl + Left/Right' keys. 6.Observe the screen reader narration here. **Observation using NVDA and JAWS screen reader:** Same issue repro with NVDA and JAWS screen reader also. **User Experience** Users who rely on screen reader may not get the info properly while navigating in mark mode. **WCAG Reference Link:** https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships **Attachment :** [Screen reader is not announcing full word information while navigating via ctrl + left_right arrow keys.zip](https://github.com/user-attachments/files/16943981/Screen.reader.is.not.announcing.full.word.information.while.navigating.via.ctrl.%2B.left_right.arrow.keys.zip) ### Expected Behavior Screen reader should narrate complete word information while navigating using ctrl + left/right arrow keys in mark mode. ### Actual Behavior Screen reader is just announcing a single character information while navigating using ctrl + left/right arrow keys in mark mode. For example: For word "Microsoft", screen reader is just announcing as 'M selected' when we navigate using 'Ctrl + Left' arrow key and announces as 't selected' using 'Ctrl + Right' arrow.
claunia commented 2026-01-31 08:07:38 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Sep 10, 2024):

This is by design. Pressing Ctrl+Left/Right moves you to the previous/next word respectively. You're just moving the cursor around, which is why the resulting announcement by the screen reader is what is selected (in the case above, "M"). If you want to expand the selection instead of just moving the cursor, you'll need to hold the Shift key.

Closing as by design.

@carlos-zamora commented on GitHub (Sep 10, 2024): This is by design. Pressing Ctrl+Left/Right moves you to the previous/next word respectively. You're just moving the cursor around, which is why the resulting announcement by the screen reader is what is selected (in the case above, "M"). If you want to expand the selection instead of just moving the cursor, you'll need to hold the Shift key. Closing as by design.
claunia commented 2026-01-31 08:07:38 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 10, 2024):

But should we perhaps narrate an entire word when the cursor position moves by more than 1 cell? That's what seems to happen when using Word at least. I'm not entirely sure how to implement this though.

@lhecker commented on GitHub (Sep 10, 2024): But should we perhaps narrate an entire word when the cursor position moves by more than 1 cell? That's what seems to happen when using Word at least. I'm not entirely sure how to implement this though.
claunia commented 2026-01-31 08:07:38 +00:00
Author
Owner
Copy Link

@Saurabh220304 commented on GitHub (Sep 11, 2024):

@carlos-zamora,
This issue is logged from the feedback of Adam Samec. As mentioned in the mail we should be able to navigate among the words using 'Ctrl + Left/Right' arrow keys.
Screen reader is just narrating as selected with single character information instead of narrating the complete word information.

@Saurabh220304 commented on GitHub (Sep 11, 2024): @carlos-zamora, This issue is logged from the feedback of Adam Samec. As mentioned in the mail we should be able to navigate among the words using 'Ctrl + Left/Right' arrow keys. Screen reader is just narrating as selected with single character information instead of narrating the complete word information.
claunia commented 2026-01-31 08:07:38 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Sep 11, 2024):

I see. Ok, reopening.

Related issues:

I suspect that fixing both of those issues may fix this one inadvertently. Totally based on a hunch, but I wonder if screen readers behave differently when the cursor moves as a degenerate range (like, maybe they automatically read out the current word since there's no selected text).

Tried looking at Word under accevent but all I got was TextSelectionChanged events, which means that the screen reader has special logic to handle that (pretty standard) then calls the UIA APIs off of the text provider.

@carlos-zamora commented on GitHub (Sep 11, 2024): I see. Ok, reopening. Related issues: - #13447 - #15787 I suspect that fixing both of those issues may fix this one inadvertently. Totally based on a hunch, but I wonder if screen readers behave differently when the cursor moves as a degenerate range (like, maybe they automatically read out the current word since there's no selected text). Tried looking at Word under accevent but all I got was TextSelectionChanged events, which means that the screen reader has special logic to handle that (pretty standard) then calls the UIA APIs off of the text provider.
claunia commented 2026-01-31 08:07:38 +00:00
Author
Owner
Copy Link

@Priyanka-Chauhan123 commented on GitHub (Jan 22, 2025):

@carlos-zamora This bug is impacting Windows Terminal product compliance and making it D. Any expected/tentative ETA by when this issue can be fixed?

@Priyanka-Chauhan123 commented on GitHub (Jan 22, 2025): @carlos-zamora This bug is impacting Windows Terminal product compliance and making it D. Any expected/tentative ETA by when this issue can be fixed?
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 A11ySev2 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal In-PR Issue-Bug Needs-Tag-Fix 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#22245
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?