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

[Screen Reader-Command Palette]:-Screen reader is not announcing the suggestions when user searches for the commands. #11001

New Issue
Closed
opened 2026-01-31 02:35:54 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:35:54 +00:00
Owner
Copy Link

Originally created by @DasaradhaKamjula on GitHub (Oct 13, 2020).

Originally assigned to: @DHowett on GitHub.

User Experience:
Users who rely on screen reader will not be able to get the suggestions info displayed on searching for commands..

Test Environment:
App: Windows Terminal Preview
Feature: Command Palette
Screen Reader: Narrator
OS: Win 10 2004 Build (19041.508)

Repro Steps:
1.Open Windows terminal Preview app
2.Open Command Palette using shortcut (Ctrl+shift+p)
3.Search for any in command in the search field
4.Observe whether screen reader is providing any announcements or not after searching for commands.

Actual:
Screen reader is not announcing the suggestions info when user searches for the commands. Screen reader remains silent on searching.

Expected:
Screen reader should provide the results info on searching commands like 10 results found or suggestions available when there are any search results and if there are no search results then it should announce as No commands found .

MAS Reference:
https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}

Originally created by @DasaradhaKamjula on GitHub (Oct 13, 2020). Originally assigned to: @DHowett on GitHub. **User Experience:** Users who rely on screen reader will not be able to get the suggestions info displayed on searching for commands.. **Test Environment:** App: Windows Terminal Preview Feature: Command Palette Screen Reader: Narrator OS: Win 10 2004 Build (19041.508) **Repro Steps:** 1.Open Windows terminal Preview app 2.Open Command Palette using shortcut (Ctrl+shift+p) 3.Search for any in command in the search field 4.Observe whether screen reader is providing any announcements or not after searching for commands. **Actual:** Screen reader is not announcing the suggestions info when user searches for the commands. Screen reader remains silent on searching. **Expected:** Screen reader should provide the results info on searching commands like 10 results found or suggestions available when there are any search results and if there are no search results then it should announce as No commands found . **MAS Reference:** https://microsoft.sharepoint.com/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
claunia commented 2026-01-31 02:35:56 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 3, 2022):

@DasaradhaKamjula This is now fixed in v1.12.10334.0. Can you please confirm?

@carlos-zamora commented on GitHub (Feb 3, 2022): @DasaradhaKamjula This is now fixed in v1.12.10334.0. Can you please confirm?
claunia commented 2026-01-31 02:35:56 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 8, 2022):

Hi @carlos-zamora @zadjii-msft

Screen Reader is only announcing 'Suggestion Available' but UX of Screen Reader users enhance if it also announces suggestion count like '2 Suggestion available'

Thanks :):

@ghost commented on GitHub (Feb 8, 2022): Hi @carlos-zamora @zadjii-msft Screen Reader is only announcing 'Suggestion Available' but UX of Screen Reader users enhance if it also announces suggestion count like '2 Suggestion available' Thanks :):
claunia commented 2026-01-31 02:35:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 8, 2022):

@v-rpundir we were concerned that localizing messages for '2 Suggestion available' might be more complicated than just formatting a message with the number of results. I can whip something up for 'one suggestion available' vs '{numResults} suggestions available', but I don't know if that'll localize super well.

In any case, do you think we could close out this A11ySev2 bug and open a new A11yUsable bug tracking adding a number to the message?

@zadjii-msft commented on GitHub (Feb 8, 2022): @v-rpundir we were concerned that localizing messages for '2 Suggestion available' might be more complicated than just formatting a message with the number of results. I can whip something up for 'one suggestion available' vs '{numResults} suggestions available', but I don't know if that'll localize super well. In any case, do you think we could close out this A11ySev2 bug and open a new A11yUsable bug tracking adding a number to the message?
claunia commented 2026-01-31 02:35:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 8, 2022):

@v-rpundir, due to a lack of localization support for the different plural word forms in different languages (Russian has 4, Arabic has 7) across the entire Windows platform, no other applications on the platform announce the numbers of search results available. Can you re-evaluate this request?

We would like to do it, for sure, but this seems like it is a new Sev3 request.

@DHowett commented on GitHub (Feb 8, 2022): @v-rpundir, due to a lack of localization support for the different plural word forms in different languages (Russian has 4, Arabic has 7) across the entire Windows platform, no other applications on the platform announce the numbers of search results available. Can you re-evaluate this request? We would like to do it, for sure, but this seems like it is a _new_ Sev3 request.
claunia commented 2026-01-31 02:35:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 18, 2022):

@v-rpundir Sorry to be a bother: the existence of suggestions is currently announced in conformity with other Windows products. This bug is resolved as well as we can, but it is still impacting our accessibility score negatively. I'm requesting that this out-of-SLA Sev2 be closed as fixed and replaced with a new Sev3 to track announcing the number of suggestions.

@DHowett commented on GitHub (Feb 18, 2022): @v-rpundir Sorry to be a bother: the existence of suggestions is currently announced in conformity with other Windows products. This bug is resolved as well as we can, but it is still impacting our accessibility score negatively. I'm requesting that this out-of-SLA Sev2 be closed as fixed and replaced with a new Sev3 to track announcing the _number_ of suggestions.
claunia commented 2026-01-31 02:35:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 19, 2022):

Closing this bug and will log new issue after discussing with PWD Users.

@ghost commented on GitHub (Feb 19, 2022): Closing this bug and will log new issue after discussing with PWD Users.
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 A11yWCAG Area-Accessibility Area-CmdPal Area-UserInterface HCL-E+D HCL-WindowsTerminal Impact-Compliance Issue-Bug Needs-Tag-Fix Priority-2 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#11001
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?