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

[Command Area]: Voice Access users are not able to type most of the symbols and punctuation marks in the command area. #18272

New Issue
Closed
opened 2026-01-31 06:08:51 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:08:51 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Aug 23, 2022).

Windows Terminal version

1.15.2003.0

Windows build number

10.0.25179.1000

Other Software

Test Environment:
OS: Window 11 22H2 OS Build 25179.1000
App: Windows Terminal Preview
AT: Voice Access

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Voice Access AT.
  3. In Command Prompt command area, try to type Asterisk, Backslash, Forward slash, Underscore, Percent Sign, Pound/Number sign, Plus, less than sign, Greater than sign, Dollar sign, Comma, Colon, Semicolon Begin/Open Single quote, End/Close single quote, Left/Open parentheses, Right/Close Parentheses, Open bracket, Close bracket, Left/Open brace, 'Right/Close brace' symbols and observe the issue.

User Experience:
People with limited mobility who use Voice Access will have bad user experience as they will not be able to execute those commands where they need to use special symbols.

Guideline Reference:
EN 301 549 V3.2.1: 11.06.02 No disruption of accessibility features

Attachments:
Special symbols.zip

Attachment Note: Not attached Code Snippet as not able to inspect Terminal Preview app with AI and Inspector tool.

Expected Behavior

Voice Access users should be able to type all of the symbols and punctuation marks in the command area.

Actual Behavior

Voice Access users are not able to type below mentioned symbols and punctuation marks in the command area.

  • Asterisk, Backslash, Forward slash, Underscore, Percent Sign, Pound/Number sign, Plus, less than sign, Greater than sign, Dollar sign, Comma, Colon, Semicolon Begin/Open Single quote, End/Close single quote, Left/Open parentheses, Right/Close Parentheses, Open bracket, Close bracket, Left/Open brace, 'Right/Close brace'.

Observation:
Voice Access users can use Onscreen keyboard to perform same task.

To learn more about Voice Access and how an application can support its different modes, Refer https://www.osgwiki.com/wiki/VoiceAccess_Testing

Voice Access Commands page: https://sway.office.com/Q5JvoIGBI5glyoKw?ref=Link

Originally created by @ghost on GitHub (Aug 23, 2022). ### Windows Terminal version 1.15.2003.0 ### Windows build number 10.0.25179.1000 ### Other Software **Test Environment:** OS: Window 11 22H2 OS Build 25179.1000 App: Windows Terminal Preview AT: Voice Access ### Steps to reproduce **Repro Steps:** 1. Open Windows Terminal. 2. Open Voice Access AT. 3. In Command Prompt command area, try to type Asterisk, Backslash, Forward slash, Underscore, Percent Sign, Pound/Number sign, Plus, less than sign, Greater than sign, Dollar sign, Comma, Colon, Semicolon Begin/Open Single quote, End/Close single quote, Left/Open parentheses, Right/Close Parentheses, Open bracket, Close bracket, Left/Open brace, 'Right/Close brace' symbols and observe the issue. **User Experience:** People with limited mobility who use Voice Access will have bad user experience as they will not be able to execute those commands where they need to use special symbols. **Guideline Reference:** EN 301 549 V3.2.1: 11.06.02 No disruption of accessibility features **Attachments:** [Special symbols.zip](https://github.com/microsoft/terminal/files/9400144/Special.symbols.zip) Attachment Note: Not attached Code Snippet as not able to inspect Terminal Preview app with AI and Inspector tool. ### Expected Behavior Voice Access users should be able to type all of the symbols and punctuation marks in the command area. ### Actual Behavior Voice Access users are not able to type below mentioned symbols and punctuation marks in the command area. - Asterisk, Backslash, Forward slash, Underscore, Percent Sign, Pound/Number sign, Plus, less than sign, Greater than sign, Dollar sign, Comma, Colon, Semicolon Begin/Open Single quote, End/Close single quote, Left/Open parentheses, Right/Close Parentheses, Open bracket, Close bracket, Left/Open brace, 'Right/Close brace'. **Observation:** Voice Access users can use Onscreen keyboard to perform same task. To learn more about Voice Access and how an application can support its different modes, Refer https://www.osgwiki.com/wiki/VoiceAccess_Testing Voice Access Commands page: https://sway.office.com/Q5JvoIGBI5glyoKw?ref=Link
claunia commented 2026-01-31 06:08:54 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 12, 2022):

@v-rpundir I'm getting these issues with other apps like Notepad and Microsoft Word too. Voice Access just shows an error saying "Please tell us which field you want to focus on.". Thus, this seems like it should be a bug filed on Voice Access itself instead of Windows Terminal or any underlying app.

Do you have guidance for any next steps here? Can we close this bug out? I don't think there's anything we can even do on our end.

@carlos-zamora commented on GitHub (Oct 12, 2022): @v-rpundir I'm getting these issues with other apps like Notepad and Microsoft Word too. Voice Access just shows an error saying "Please tell us which field you want to focus on.". Thus, this seems like it should be a bug filed on Voice Access itself instead of Windows Terminal or any underlying app. Do you have guidance for any next steps here? Can we close this bug out? I don't think there's anything we can even do on our end.
claunia commented 2026-01-31 06:08:55 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 12, 2022):

@carlos-zamora we will follow external bug process here, so I am forwarding this bug to Voice Access team and will update external tracking ID when I get it.

You can resolve or close this bug with resolved reason External.

@ghost commented on GitHub (Oct 12, 2022): @carlos-zamora we will follow external bug process here, so I am forwarding this bug to Voice Access team and will update external tracking ID when I get it. You can resolve or close this bug with resolved reason External.
claunia commented 2026-01-31 06:08:55 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 17, 2022):

Voice Access Tracking ID: Bug 41814107: [Voice Access] : Voice Access users are unable to input symbols and punctuation marks in the terminal

@ghost commented on GitHub (Oct 17, 2022): Voice Access Tracking ID: [Bug 41814107](https://microsoft.visualstudio.com/OS/_workitems/edit/41814107): [Voice Access] : Voice Access users are unable to input symbols and punctuation marks in the terminal
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 A11ySev2 A11yWCAG Area-Accessibility Disability-Mobility HCL-E+D HCL-WindowsTerminal Issue-Bug Priority-2 Product-Terminal Resolution-External 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#18272
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?