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

[PR #19726] Improve screen reader announcements for search box #31937

New Issue
Open
opened 2026-01-31 09:50:30 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:50:30 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/19726

State: closed
Merged: Yes

Summary of the Pull Request

Improves the notification read out by a screen reader when a search is done in the terminal. This is done across several scenarios:

  • previously, the results were only read occasionally. Moving the block out of if (results.SearchInvalidated) fixes that.
  • previously, we read "Results found" or "No results found". Now, we read an accessible version of the written status message.

In order to maintain consistency with the written status message, _FormatText() now takes an isAccessible parameter to output a more accessible version of the text. Specifically...

  • CurrentIndexTooHighStatus (aka ?) would not be read, so we replace it with TermControl_UnknownSearchResultIndex (aka unknown)
  • TermControl_TooManySearchResults (aka 999+) would drop the + when read, so we replace it with TermControl_TooManySearchResults (aka over 999)
  • TermControl_NumResults (aka {0}/{1}``) would be read as a fraction, so we replace it with TermControl_NumResultsAccessible(aka{0} of {1}`).

Validation Steps Performed

✅ Announcements are read out when interacting with search box (i.e. next, prev, regex toggle, etc.)
✅ "4 of 5" read out by screen reader (or something similar) when search is performed

Closes #19691

**Original Pull Request:** https://github.com/microsoft/terminal/pull/19726 **State:** closed **Merged:** Yes --- ## Summary of the Pull Request Improves the notification read out by a screen reader when a search is done in the terminal. This is done across several scenarios: - previously, the results were only read occasionally. Moving the block out of `if (results.SearchInvalidated)` fixes that. - previously, we read "Results found" or "No results found". Now, we read an accessible version of the written status message. In order to maintain consistency with the written status message, `_FormatText()` now takes an `isAccessible` parameter to output a more accessible version of the text. Specifically... - `CurrentIndexTooHighStatus` (aka `?`) would not be read, so we replace it with `TermControl_UnknownSearchResultIndex` (aka `unknown`) - `TermControl_TooManySearchResults` (aka `999+`) would drop the `+` when read, so we replace it with `TermControl_TooManySearchResults` (aka `over 999`) - `TermControl_NumResults` (aka `{0}/{1}``) would be read as a fraction, so we replace it with `TermControl_NumResultsAccessible` (aka `{0} of {1}`). ## Validation Steps Performed ✅ Announcements are read out when interacting with search box (i.e. next, prev, regex toggle, etc.) ✅ "4 of 5" read out by screen reader (or something similar) when search is performed Closes #19691
claunia added the pull-request label 2026-01-31 09:50:30 +00:00
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 pull-request
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#31937
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?