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

A11y_Windows Terminal_Search or Find Operation_Screen Reader: After entering the text and performing search operation the screen reader is not reading whether that particular word is present or not in the terminal #7505

New Issue
Closed
opened 2026-01-31 01:05:39 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:05:39 +00:00
Owner
Copy Link

Originally created by @SpandanaPaladi on GitHub (Apr 20, 2020).

#A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ScreenReader; #Narrator; #NVDA; #A11ySev2; #NonBenchMark; #MAS1.3.1

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier

Environment Details:
Version: 0.10.781.0

Repro steps:

  1. Turn on screen reader
  2. Hit the URL ""aka.ms/terminal"" and install ""Windows terminal (Preview)"" application
  3. Open ""Windows terminal (Preview)"" application
  4. Use "Alt + Shift + F" to perform search/find operation
  5. Verify whether the screen reader is reading that particular word which is searched is present in the terminal or not

Actual Result:
Narrator/NVDA is not reading whether the searched word is present in the terminal or not

Expected Result:​
Narrator/NVDA should read whether the searched word is present in the terminal or not

User Impact:​
Screen Reader users will face difficulty if the screen reader don't read whether the searched word is present or not in the terminal because they don't understand whether the searched word is present or not

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

Bug_Narrator not reading the searched word.pptx
Bug_NVDA not reading the searched word.pptx

Originally created by @SpandanaPaladi on GitHub (Apr 20, 2020). #A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ScreenReader; #Narrator; #NVDA; #A11ySev2; #NonBenchMark; #MAS1.3.1 [Check out Accessibility Insights!](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-shcha1%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458847087032&sdata=uWx6cTEfazn%2BoCV3cL1iYB4KN%2BuXQ/MTlmOVec%2BZgKc%3D&reserved=0) - Identify accessibility bugs before check-in and make bug fixing faster and easier **Environment Details:** Version: 0.10.781.0 **Repro steps:** 1. Turn on screen reader 2. Hit the URL ""aka.ms/terminal"" and install ""Windows terminal (Preview)"" application 3. Open ""Windows terminal (Preview)"" application 4. Use "Alt + Shift + F" to perform search/find operation 5. Verify whether the screen reader is reading that particular word which is searched is present in the terminal or not **Actual Result:** Narrator/NVDA is not reading whether the searched word is present in the terminal or not **Expected Result:​** Narrator/NVDA should read whether the searched word is present in the terminal or not **User Impact:​** Screen Reader users will face difficulty if the screen reader don't read whether the searched word is present or not in the terminal because they don't understand whether the searched word is present or not **MAS Reference:​** https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4} [Bug_Narrator not reading the searched word.pptx](https://github.com/microsoft/terminal/files/4502959/Bug_Narrator.not.reading.the.searched.word.pptx) [Bug_NVDA not reading the searched word.pptx](https://github.com/microsoft/terminal/files/4502962/Bug_NVDA.not.reading.the.searched.word.pptx)
claunia commented 2026-01-31 01:05:40 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (May 19, 2020):

@SpandanaPaladi are you still seeing this issue, or can we close it?

@carlos-zamora commented on GitHub (May 19, 2020): @SpandanaPaladi are you still seeing this issue, or can we close it?
claunia commented 2026-01-31 01:05:40 +00:00
Author
Owner
Copy Link

@Neurrone commented on GitHub (May 22, 2020):

when the search term is not found, pressing enter on the find dialog announces nothing. It would be ideal if some message was announced to the effect that it was not found.

When it is found, NVDA reads the search term. I find that this behaviour is not that intuitive.

What does work well is that when escaping out of the find dialog, NVDA's review cursor is positioned at the starting position of the match for you to review around it.

@Neurrone commented on GitHub (May 22, 2020): when the search term is not found, pressing enter on the find dialog announces nothing. It would be ideal if some message was announced to the effect that it was not found. When it is found, NVDA reads the search term. I find that this behaviour is not that intuitive. What does work well is that when escaping out of the find dialog, NVDA's review cursor is positioned at the starting position of the match for you to review around it.
claunia commented 2026-01-31 01:05:40 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jun 2, 2020):

@SpandanaPaladi are we compliant given the current state? Can we close this issue?

@Neurrone What you're requesting is a good idea, but I think with regards to tracking, it's slightly separate from what this issue is talking about. That said, I've opened issue #6319 to track it.

@carlos-zamora commented on GitHub (Jun 2, 2020): @SpandanaPaladi are we compliant given the current state? Can we close this issue? @Neurrone What you're requesting is a good idea, but I think with regards to tracking, it's slightly separate from what this issue is talking about. That said, I've opened issue #6319 to track it.
claunia commented 2026-01-31 01:05:40 +00:00
Author
Owner
Copy Link

@Neurrone commented on GitHub (Jun 3, 2020):

Looking at the issue title, I think it should remain open because nothing is read if no matches are found.

I agree that the UX for when text is found and how its conveyed should be in its own issue.

@Neurrone commented on GitHub (Jun 3, 2020): Looking at the issue title, I think it should remain open because nothing is read if no matches are found. I agree that the UX for when text is found and how its conveyed should be in its own issue.
claunia commented 2026-01-31 01:05:40 +00:00
Author
Owner
Copy Link

@Neurrone commented on GitHub (Jun 3, 2020):

Oh, I see why you split it off in its own issue. I don't mind closing this or leaving this open while the proper UX is implemented in #6319.

@Neurrone commented on GitHub (Jun 3, 2020): Oh, I see why you split it off in its own issue. I don't mind closing this or leaving this open while the proper UX is implemented in #6319.
claunia commented 2026-01-31 01:05:40 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (Jun 12, 2020):

Now NVDA is reading regarding the searched keyword but Narrator is not reading anything. Still able to reproduce the issue with Narrator.

[Not Fixed]Bug 5421_Narrator not reading regarding searched keyword.pptx

Bug 5421_NVDA is reading when user search any keyword.pptx

@Amulya-95 commented on GitHub (Jun 12, 2020): Now NVDA is reading regarding the searched keyword but Narrator is not reading anything. Still able to reproduce the issue with Narrator. [[Not Fixed]Bug 5421_Narrator not reading regarding searched keyword.pptx](https://github.com/microsoft/terminal/files/4771047/Not.Fixed.Bug.5421_Narrator.not.reading.regarding.searched.keyword.pptx) [Bug 5421_NVDA is reading when user search any keyword.pptx](https://github.com/microsoft/terminal/files/4771324/Bug.5421_NVDA.is.reading.when.user.search.any.keyword.pptx)
claunia commented 2026-01-31 01:05:41 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (Jun 17, 2020):

Please provide the Sample app, so that we will file bug to Narrator team and will close the current bug as it is working fine with another free screen reader (NVDA)

@Amulya-95 commented on GitHub (Jun 17, 2020): Please provide the Sample app, so that we will file bug to Narrator team and will close the current bug as it is working fine with another free screen reader (NVDA)
claunia commented 2026-01-31 01:05:41 +00:00
Author
Owner
Copy Link

@SpandanaPaladi commented on GitHub (Jun 19, 2020):

Logged External bug https://microsoft.visualstudio.com/OS/_workitems/edit/27084958 to Narrator team.

Closing the current bug as it is working fine with NVDA

@SpandanaPaladi commented on GitHub (Jun 19, 2020): Logged External bug https://microsoft.visualstudio.com/OS/_workitems/edit/27084958 to Narrator team. Closing the current bug as it is working fine with NVDA
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 Area-Accessibility Issue-Bug Product-Terminal Resolution-Fix-Committed
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#7505
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?