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

[Freeway-bug][Windows terminal>New Tab]: Voice Access number is not defined for ‘New Tab’ split button. #23929

New Issue
Closed
opened 2026-01-31 08:56:29 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:56:29 +00:00
Owner
Copy Link

Originally created by @Saurabh220304 on GitHub (Dec 31, 2025).

Windows Terminal version

1.25.3571.0

Windows build number

Windows 11 Version 26H1 (OS Build 28000.1340)

Other Software

No response

Steps to reproduce

Steps for turning on Voice access:
Settings>Accessibility>Speech>Voice Access.

Repro Steps:
1.Launch the Window terminal app.
2.Terminal home page will open.
3.Turn on voice access by following above mentioned steps.
4.Now give show number command.
5.Observe the issue here.

User Experience:
Users who rely on Voice Access cannot interact with the ‘New Tab’ split button, making it impossible to perform the intended action without switching to touch or keyboard input. This creates a barrier for users with motor disabilities who depend on voice commands for navigation and activation.

WCAG Reference Link:
https://aka.ms/MAS4.3.1

Attachements:
https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-heparihar_microsoft_com/IQD7F3qbSJSJRqpC9tH6zfkdAcs0pXKs1sEut9tIpE8bJHI?e=wz5TyF

Expected Behavior

The ‘New Tab’ split button should have a unique Voice Access number assigned so that users can activate it using voice commands.

Actual Behavior

Voice Access number is not defined for ‘New Tab’ split button. Users cannot activate this control using voice commands.

Originally created by @Saurabh220304 on GitHub (Dec 31, 2025). ### Windows Terminal version 1.25.3571.0 ### Windows build number Windows 11 Version 26H1 (OS Build 28000.1340) ### Other Software _No response_ ### Steps to reproduce **Steps for turning on Voice access:** Settings>Accessibility>Speech>Voice Access. **Repro Steps:** 1.Launch the Window terminal app. 2.Terminal home page will open. 3.Turn on voice access by following above mentioned steps. 4.Now give show number command. 5.Observe the issue here. User Experience: Users who rely on Voice Access cannot interact with the ‘New Tab’ split button, making it impossible to perform the intended action without switching to touch or keyboard input. This creates a barrier for users with motor disabilities who depend on voice commands for navigation and activation. WCAG Reference Link: https://aka.ms/MAS4.3.1 Attachements: https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-heparihar_microsoft_com/IQD7F3qbSJSJRqpC9tH6zfkdAcs0pXKs1sEut9tIpE8bJHI?e=wz5TyF ### Expected Behavior The ‘New Tab’ split button should have a unique Voice Access number assigned so that users can activate it using voice commands. ### Actual Behavior Voice Access number is not defined for ‘New Tab’ split button. Users cannot activate this control using voice commands.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:56:29 +00:00
claunia commented 2026-01-31 08:56:30 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 5, 2026):

Thanks for filing! This is actually a /duplicate of #13804 which can be traced to an upstream XAML issue at https://github.com/microsoft/microsoft-ui-xaml/issues/7818.

According to XAML, this is an issue with Voice Access itself.

@carlos-zamora commented on GitHub (Jan 5, 2026): Thanks for filing! This is actually a /duplicate of #13804 which can be traced to an upstream XAML issue at https://github.com/microsoft/microsoft-ui-xaml/issues/7818. [According to XAML](https://github.com/microsoft/microsoft-ui-xaml/issues/7818#issuecomment-1854854954), this is an issue with Voice Access itself.
claunia commented 2026-01-31 08:56:30 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jan 5, 2026):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Jan 5, 2026): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Issue-Bug Resolution-Duplicate
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#23929
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?