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 - Windows Powershell]: User is not able to navigate in edit area of powershell in scan mode of the narrator. #11676

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

Originally created by @Chandresh1007 on GitHub (Dec 3, 2020).

Originally assigned to: @carlos-zamora on GitHub.

User Experience:
User who rely on screen reader will be affected if the the screen reader focus does not navigate to the edit area of windows powershell as the screen reader users will not able to navigate to the contents of the page .

Test Environment:
OS: Win 10 2004 Build (20262.1010)
App: Windows Terminal
App version: 1.4.3243.0

Repro Steps:

  1. Open Windows terminal app.
  2. Launch Narrator.
  3. Turn on the scan mode of the narrator using "Caps+Space".
  4. Now navigate using Up/Down arrow key.
  5. Observe the issue.

Actual Result:
User is not able to navigate in edit area of powershell in scan mode of the narrator.

Expected Result:
In scan mode screen reader focus should navigate to the edit area of powershell and read the text.

Note: NVDA browse mode is not working.

MAS Reference:
MAS4.2.10
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7Bb24201d1-2276-4471-8183-e1e5353031ad%7D&cid=83352b15-6eaa-4fc1-bd5a-2d857a532986

MAS4.2.10_Scan mode_not navigating to powershell window text.zip

Originally created by @Chandresh1007 on GitHub (Dec 3, 2020). Originally assigned to: @carlos-zamora on GitHub. **User Experience:** User who rely on screen reader will be affected if the the screen reader focus does not navigate to the edit area of windows powershell as the screen reader users will not able to navigate to the contents of the page . **Test Environment:** OS: Win 10 2004 Build (20262.1010) App: Windows Terminal App version: 1.4.3243.0 **Repro Steps:** 1. Open Windows terminal app. 2. Launch Narrator. 3. Turn on the scan mode of the narrator using "Caps+Space". 4. Now navigate using Up/Down arrow key. 5. Observe the issue. **Actual Result:** User is not able to navigate in edit area of powershell in scan mode of the narrator. **Expected Result:** In scan mode screen reader focus **should navigate to the edit area of powershell and read the text**. **Note:** NVDA browse mode is not working. **MAS Reference:** MAS4.2.10 https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7Bb24201d1-2276-4471-8183-e1e5353031ad%7D&cid=83352b15-6eaa-4fc1-bd5a-2d857a532986 [MAS4.2.10_Scan mode_not navigating to powershell window text.zip](https://github.com/microsoft/terminal/files/5635390/MAS4.2.10_Scan.mode_not.navigating.to.powershell.window.text.zip)
claunia commented 2026-01-31 02:54:26 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 3, 2020):

After watching the attached video, there's two issues here:

  1. When you return focus back to the text area, you actually exited scan mode. That's why the arrow keys navigate through the history and the command prompt area. If you enter scan mode again, you should be able to navigate the buffer properly.
  2. When you exited scan mode on accident, the screen reader wasn't reading the new commands injected in the command prompt. This is the same as https://github.com/microsoft/terminal/issues/8463. NVDA does not have this issue.

Can we close this issue as invalid? Again, if you enter scan mode when in the text area, scan mode should work just fine.

@carlos-zamora commented on GitHub (Dec 3, 2020): After watching the attached video, there's two issues here: 1. When you return focus back to the text area, you actually exited scan mode. That's why the arrow keys navigate through the history and the command prompt area. If you enter scan mode again, you should be able to navigate the buffer properly. 2. When you exited scan mode on accident, the screen reader wasn't reading the new commands injected in the command prompt. This is the same as https://github.com/microsoft/terminal/issues/8463. NVDA does not have this issue. Can we close this issue as invalid? Again, if you enter scan mode when in the text area, scan mode should work just fine.
claunia commented 2026-01-31 02:54:26 +00:00
Author
Owner
Copy Link

@Chandresh1007 commented on GitHub (Dec 7, 2020):

@carlos-zamora For 1st point, we are still not satisfied as user is still not able to access the text of the edit area in scan mode of the narrator even after turning it on again.
Should we log this against narrator if the issue is not at the windows terminal end?

@Chandresh1007 commented on GitHub (Dec 7, 2020): @carlos-zamora For 1st point, we are still not satisfied as user is still not able to access the text of the edit area in scan mode of the narrator even after turning it on again. Should we log this against narrator if the issue is not at the windows terminal end?
claunia commented 2026-01-31 02:54:26 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 7, 2020):

@Chandresh1007 I don't know how to record my screen with audio (sorry), but I know how to take a gif haha. I've attached it below. You can see the bounding rectangles for text that is being read. It seems to be working just fine with the repro steps provided above. Do you mind sending a video of this second attempt?

Narrator - Scan Mode Demo

@carlos-zamora commented on GitHub (Dec 7, 2020): @Chandresh1007 I don't know how to record my screen with audio (sorry), but I know how to take a gif haha. I've attached it below. You can see the bounding rectangles for text that is being read. It seems to be working just fine with the repro steps provided above. Do you mind sending a video of this second attempt? ![Narrator - Scan Mode Demo](https://user-images.githubusercontent.com/11050425/101382148-770e9580-386c-11eb-8be7-5e27f43b8376.gif)
claunia commented 2026-01-31 02:54:26 +00:00
Author
Owner
Copy Link

@Chandresh1007 commented on GitHub (Dec 8, 2020):

@carlos-zamora Please find the attached video
Terminal_Scan mode issue.zip

@Chandresh1007 commented on GitHub (Dec 8, 2020): @carlos-zamora Please find the attached video [Terminal_Scan mode issue.zip](https://github.com/microsoft/terminal/files/5659041/Terminal_Scan.mode.issue.zip)
claunia commented 2026-01-31 02:54:26 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 8, 2020):

@carlos-zamora Please find the attached video
Terminal_Scan mode issue.zip

I see what's going on now. So, you entered Scan Mode, then used the up/down arrows to navigate to the next/previous item. At the 0:36 mark, Scan Mode is turned off for you. At 0:46, you enter Scan Mode again, but then you press up/down. Doing so does not navigate the text area, because, as mentioned before, this is used to navigate to the next/previous item. When you enter scan mode in the text area, you want to use these keybindings:

Task Command
Next/Previous Line ctrl+up/down
Next/Previous Character right/left
Next/Previous word ctrl+right/left

Source: Narrator Keyboard Shortcuts

@carlos-zamora commented on GitHub (Dec 8, 2020): > @carlos-zamora Please find the attached video > [Terminal_Scan mode issue.zip](https://github.com/microsoft/terminal/files/5659041/Terminal_Scan.mode.issue.zip) I see what's going on now. So, you entered Scan Mode, then used the up/down arrows to navigate to the next/previous item. At the 0:36 mark, Scan Mode is turned off for you. At 0:46, you enter Scan Mode again, but then you press up/down. Doing so does not navigate the text area, because, as mentioned before, this is used to navigate to the next/previous item. When you enter scan mode in the text area, you want to use these keybindings: | Task | Command | |--|--| | Next/Previous Line | ctrl+up/down | | Next/Previous Character | right/left | | Next/Previous word | ctrl+right/left | Source: [Narrator Keyboard Shortcuts](https://dequeuniversity.com/screenreaders/narrator-keyboard-shortcuts)
claunia commented 2026-01-31 02:54:27 +00:00
Author
Owner
Copy Link

@Chandresh1007 commented on GitHub (Dec 9, 2020):

@carlos-zamora Yes, with the above mentioned keybindings, I am able to navigate text area in the scan mode. Thanks!

@Chandresh1007 commented on GitHub (Dec 9, 2020): @carlos-zamora Yes, with the above mentioned keybindings, I am able to navigate text area in the scan mode. Thanks!
claunia commented 2026-01-31 02:54:27 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 9, 2020):

@carlos-zamora Yes, with the above mentioned keybindings, I am able to navigate text area in the scan mode. Thanks!

Haven't been following what the correct procedure now is, but can we close this issue then?

@carlos-zamora commented on GitHub (Dec 9, 2020): > @carlos-zamora Yes, with the above mentioned keybindings, I am able to navigate text area in the scan mode. Thanks! Haven't been following what the correct procedure now is, but can we close this issue then?
claunia commented 2026-01-31 02:54:27 +00:00
Author
Owner
Copy Link

@Chandresh1007 commented on GitHub (Dec 15, 2020):

Closing this issue as we are able to navigate the text area in scan mode using keybindings as mentioned above.

@Chandresh1007 commented on GitHub (Dec 15, 2020): Closing this issue as we are able to navigate the text area in scan mode using keybindings as mentioned above.
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 A11yTTValidated A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix Priority-0 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#11676
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?