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

[Windows Terminal]: Narrator only announce 'space space' when user navigate through commands using up or down arrow keys. #16086

New Issue
Closed
opened 2026-01-31 04:57:09 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 04:57:09 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Dec 9, 2021).

Windows Terminal version

1.12.2931.0

Windows build number

10.0.22504.1010

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator
Tool: Accessibility Insights for Windows Version 1.1.1741.1

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Narrator using 'Win + Ctrl + Enter' key and ensure Scan mode is OFF.(Turn on Scan on mode using 'Caps lock + Space' keys).
  3. Inside Command Prompt/PowerShell, Execute different commands then navigate through used commands using 'up' or 'down arrow' keys.
  4. Observe the issue.

User Experience:
Screen Reader user will be impacted here if they didn't get the information which appear on screen and announcing incorrect information.

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

Attachments:
Narrator.only.announce.space.space.....zip

Expected Behavior

Narrator should announce command name when user navigate through commands using up or down arrow keys.

Actual Behavior

Narrator only announce 'space space' when user navigate through commands using up or down arrow keys. When we navigate using up arrow key then issue only repro when previous and next command initials are same.

Note Issue: Same issue repro when we press tab or Shift+ tab to navigate through all directory names.

Observation: Issue not repro with NVDA Screen Reader.

Originally created by @ghost on GitHub (Dec 9, 2021). ### Windows Terminal version 1.12.2931.0 ### Windows build number 10.0.22504.1010 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 22504.1010) App: Windows Terminal Preview Screen Reader: Narrator Tool: Accessibility Insights for Windows Version 1.1.1741.1 ### Steps to reproduce **Repro Steps:** 1. Open Windows Terminal. 3. Open Narrator using 'Win + Ctrl + Enter' key and ensure Scan mode is OFF.(Turn on Scan on mode using 'Caps lock + Space' keys). 4. Inside Command Prompt/PowerShell, Execute different commands then navigate through used commands using 'up' or 'down arrow' keys. 5. Observe the issue. **User Experience:** Screen Reader user will be impacted here if they didn't get the information which appear on screen and announcing incorrect information. **Guideline Reference:** https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships **Attachments:** [Narrator.only.announce.space.space.....zip](https://github.com/microsoft/terminal/files/7690181/Narrator.only.announce.space.space.zip) ### Expected Behavior Narrator should announce command name when user navigate through commands using up or down arrow keys. ### Actual Behavior Narrator only announce 'space space' when user navigate through commands using up or down arrow keys. When we navigate using up arrow key then issue only repro when previous and next command initials are same. **Note Issue:** Same issue repro when we press tab or Shift+ tab to navigate through all directory names. **Observation:** Issue not repro with NVDA Screen Reader.
claunia commented 2026-01-31 04:57:11 +00:00
Author
Owner
Copy Link

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

Tested this today on version 1.21.2361.0 and it no longer repros. We must've fixed this a while back.

This also should have probably been classified as higher severity. Looking at the video, it's pretty bad that we weren't reading changes to the prompt. Good thing it's fixed!

@carlos-zamora commented on GitHub (Sep 11, 2024): Tested this today on version 1.21.2361.0 and it no longer repros. We must've fixed this a while back. This also should have probably been classified as higher severity. Looking at the video, it's pretty bad that we weren't reading changes to the prompt. Good thing it's 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 A11yCO A11ySev3 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix 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#16086
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?