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

{Freeway-Bug} [Windows Terminal - Settings]: 'Open JSON file' control in 'Settings' page does not activate using Voice Access show numbers and click commands. #23124

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

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

Originally assigned to: @carlos-zamora on GitHub.

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 the 'Settings' page.
  4. Now give voice access show numbers and click commands and try to activate 'Open JSON file' control.
  5. Observe the issue here.

User experience:
This issue impacts Voice Access users who rely on speech commands for navigation and interaction. The inability to activate the control limits accessibility and usability, preventing users from accessing JSON configuration files via voice commands.

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

Attachment:
Not able to activate 'Open JSON file' using voice access..zip

Expected Behavior

The 'Open JSON file' control should activate when the user issues the "Click Open JSON file" command via Voice Access. Selecting the control via "Show numbers" should also allow activation when the corresponding command is given.

Actual Behavior

The 'Open JSON file' control is focused when using Voice Access commands, but it does not get activated. When saying "Show numbers" and selecting the number corresponding to the control, it only gets focused. Similarly, when using the "Click Open JSON file" command, the control is focused instead of activated.

Originally created by @Saurabh220304 on GitHub (Apr 8, 2025). Originally assigned to: @carlos-zamora on GitHub. ### 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 the 'Settings' page. 4. Now give voice access show numbers and click commands and try to activate 'Open JSON file' control. 5. Observe the issue here. **User experience:** This issue impacts Voice Access users who rely on speech commands for navigation and interaction. The inability to activate the control limits accessibility and usability, preventing users from accessing JSON configuration files via voice commands. **MAS Reference Link:** https://liquid.microsoft.com/Web/Object/Read/ms.accessibility/Requirements/04.03.01 **Attachment:** [Not able to activate 'Open JSON file' using voice access..zip](https://github.com/user-attachments/files/19647323/Not.able.to.activate.Open.JSON.file.using.voice.access.zip) ### Expected Behavior The 'Open JSON file' control should activate when the user issues the "Click Open JSON file" command via Voice Access. Selecting the control via "Show numbers" should also allow activation when the corresponding command is given. ### Actual Behavior The 'Open JSON file' control is focused when using Voice Access commands, but it does not get activated. When saying "Show numbers" and selecting the number corresponding to the control, it only gets focused. Similarly, when using the "Click Open JSON file" command, the control is focused instead of activated.
claunia commented 2026-01-31 08:33:10 +00:00
Author
Owner
Copy Link

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

We've found some similar issues:

  • #12003 , 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: - #12003 , 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.
claunia commented 2026-01-31 08:33:10 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 22, 2025):

Took a look at this today. It looks very similar to #12003. For some reason, invoking the NavItem in the footer via scan mode and Voice Access selects the item, but doesn't invoke it. We have a Tapped and KeyDown handler but they never get called.

As a possible workaround, I'm considering tracking the Navigation View's SelectedItem property. Maybe we can use that to our advantage and if the selected item changes to the footer item, we invoke it. It's hacky, but it might work.

@carlos-zamora commented on GitHub (Apr 22, 2025): Took a look at this today. It looks _very_ similar to #12003. For some reason, invoking the NavItem _in the footer_ via scan mode and Voice Access selects the item, but doesn't invoke it. We have a Tapped and KeyDown handler but they never get called. As a possible workaround, I'm considering tracking the Navigation View's `SelectedItem` property. Maybe we can use that to our advantage and if the selected item changes to the footer item, we invoke it. It's hacky, but it might work.
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 A11yVoiceAccess A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix Priority-1 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#23124
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?