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

{Freeway-Bug} [Windows Terminal]: 'Open New Tab' button does not expand using Voice Access commands. #23127

New Issue
Open
opened 2026-01-31 08:33:12 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:33:12 +00:00
Owner
Copy Link

Originally created by @Saurabh220304 on GitHub (Apr 8, 2025).

Windows Terminal version

1.23.10732.0

Windows build number

27823.1000

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 27823.1000)
App: Windows Terminal Preview
Screen Reader: Narrator
Tools: Voice Access

Steps to reproduce

Pre-requisite:
Settings>Accessibility>Speech>Voice Access.

Repro steps:

  1. Open the 'windows terminal' application.
  2. Follow the above-mentioned pre-requisite step.
  3. Navigate to 'Open New Tab' control.
  4. Now give 'Show numbers' command to Voice Access.
  5. Observe whether Voice Access assigns a number to the 'Open New Tab' button.
  6. Attempt to expand the button using the "Click Expand Open New Tab" command.
  7. Observe the behavior when executing the command.
  8. Observe the issue here.

User experience:
This issue limits the usability of Voice Access for users who rely on speech commands for navigation and interaction. Without proper number assignment or activation behavior, users are unable to fully control the terminal, reducing efficiency and accessibility.

MAS Reference Link:
https://liquid.microsoft.com/Web/Object/Read/ms.accessibility/Requirements/04.03.01

Attachment:
Voice access commands are not working properly for open tab expand button.zip

Expected Behavior

Voice Access should correctly assign a number to the 'Open New Tab' button when using the "Show numbers" command. Additionally, when issuing the "Click Expand Open New Tab" command, the button should expand and display the menu options, rather than just receiving focus.

Actual Behavior

When using "Show numbers" command, Voice Access does not assign a number to the expandable 'Open New Tab' button. When attempting to activate it via "Click Expand Open New Tab," the button is only focused instead of opening the menu options.

Originally created by @Saurabh220304 on GitHub (Apr 8, 2025). ### Windows Terminal version 1.23.10732.0 ### Windows build number 27823.1000 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 27823.1000) App: Windows Terminal Preview Screen Reader: Narrator Tools: Voice Access ### Steps to reproduce **Pre-requisite:** Settings>Accessibility>Speech>Voice Access. **Repro steps:** 1. Open the 'windows terminal' application. 2. Follow the above-mentioned pre-requisite step. 3. Navigate to 'Open New Tab' control. 4. Now give 'Show numbers' command to Voice Access. 5. Observe whether Voice Access assigns a number to the 'Open New Tab' button. 6. Attempt to expand the button using the "Click Expand Open New Tab" command. 7. Observe the behavior when executing the command. 8. Observe the issue here. **User experience:** This issue limits the usability of Voice Access for users who rely on speech commands for navigation and interaction. Without proper number assignment or activation behavior, users are unable to fully control the terminal, reducing efficiency and accessibility. **MAS Reference Link:** https://liquid.microsoft.com/Web/Object/Read/ms.accessibility/Requirements/04.03.01 **Attachment:** [Voice access commands are not working properly for open tab expand button.zip](https://github.com/user-attachments/files/19647695/Voice.access.commands.are.not.working.properly.for.open.tab.expand.button.zip) ### Expected Behavior Voice Access should correctly assign a number to the 'Open New Tab' button when using the "Show numbers" command. Additionally, when issuing the "Click Expand Open New Tab" command, the button should expand and display the menu options, rather than just receiving focus. ### Actual Behavior When using "Show numbers" command, Voice Access does not assign a number to the expandable 'Open New Tab' button. When attempting to activate it via "Click Expand Open New Tab," the button is only focused instead of opening the menu options.
claunia commented 2026-01-31 08:33:13 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Apr 8, 2025):

We've found some similar issues:

  • #18770 , similarity score: 83%
  • #14391 , similarity score: 83%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Apr 8, 2025): We've found some similar issues: - #18770 , similarity score: 83% - #14391 , similarity score: 83% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
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 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#23127
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?