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

[Terminal]: JAWS Screen Reader Cursor mode does not work inside Terminal app. #16281

New Issue
Open
opened 2026-01-31 05:02:37 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:02:37 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Dec 28, 2021).

Windows Terminal version

1.12.3472.0

Windows build number

10.0.22504.1010

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: JAWS 2021

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. Activate 'Actions' tab and then Add a new actions 'Set tab color' with shortcut key 'Ctrl + Shift + c'.
  4. Open JAWS 2021 Screen Reader.
  5. Navigate inside Terminal window.
  6. Turn on Cursor mode using 'Insert + Z' and then try to read static/non-interactive/non-tab able content.
  7. Observe the issues.

User Experience:
JAWS Screen Reader users are impacted here as JAWS users are not able to read static/non-interactive/non-tab able content.

Attachments:
JAWS Screen Reader Cursor mode does not work inside Terminal app..zip

Expected Behavior

JAWS Cursor mode should work inside Terminal app.

Actual Behavior

JAWS Screen Reader Cursor mode does not work inside Terminal app as result JAWS users are not able to read static/non-interactive/non-tab able content.

Observation:
Issue does not repro with Narrator & NVDA as Scan mode work fine inside Terminal app.

Originally created by @ghost on GitHub (Dec 28, 2021). ### Windows Terminal version 1.12.3472.0 ### Windows build number 10.0.22504.1010 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 22504.1010) App: Windows Terminal Preview Screen Reader: JAWS 2021 ### Steps to reproduce **Repro Steps:** 1. Open Windows Terminal. 2. Open Settings page using 'Ctr+,'. 3. Activate 'Actions' tab and then Add a new actions 'Set tab color' with shortcut key 'Ctrl + Shift + c'. 4. Open JAWS 2021 Screen Reader. 5. Navigate inside Terminal window. 6. Turn on Cursor mode using 'Insert + Z' and then try to read static/non-interactive/non-tab able content. 7. Observe the issues. **User Experience:** JAWS Screen Reader users are impacted here as JAWS users are not able to read static/non-interactive/non-tab able content. **Attachments:** [JAWS Screen Reader Cursor mode does not work inside Terminal app..zip](https://github.com/microsoft/terminal/files/7782791/JAWS.Screen.Reader.Cursor.mode.does.not.work.inside.Terminal.app.zip) ### Expected Behavior JAWS Cursor mode should work inside Terminal app. ### Actual Behavior JAWS Screen Reader Cursor mode does not work inside Terminal app as result JAWS users are not able to read static/non-interactive/non-tab able content. **Observation:** Issue does not repro with Narrator & NVDA as Scan mode work fine inside Terminal app.
claunia commented 2026-01-31 05:02:38 +00:00
Author
Owner
Copy Link

@akash07k commented on GitHub (Feb 16, 2022):

JAWS virtual cursor only works in web apps or DOM.
Since terminal is not a web app here Virtual cursor won't work.
It's the default behaviour of jaws and messing with will lead to bad user experience

@akash07k commented on GitHub (Feb 16, 2022): JAWS virtual cursor only works in web apps or DOM. Since terminal is not a web app here Virtual cursor won't work. It's the default behaviour of jaws and messing with will lead to bad user experience
claunia commented 2026-01-31 05:02:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 23, 2022):

@akash07k Ok but it is impacting for JAWS users as JAWS Screen Reader users will not able read non-interactive text on the Terminal app?
Is this bug which only JAWS team can fix?

Thanks :):

@ghost commented on GitHub (Aug 23, 2022): @akash07k Ok but it is impacting for JAWS users as JAWS Screen Reader users will not able read non-interactive text on the Terminal app? Is this bug which only JAWS team can fix? Thanks :):
claunia commented 2026-01-31 05:02:39 +00:00
Author
Owner
Copy Link

@akash07k commented on GitHub (Aug 23, 2022):

@v-rpundir Routing JAWS Cursor to PC cursor works in this case.

@akash07k commented on GitHub (Aug 23, 2022): @v-rpundir Routing JAWS Cursor to PC cursor works in this case.
claunia commented 2026-01-31 05:02:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 23, 2022):

This does feel like something that JAWS might have to fix. Curious that it doesn't mention "UWP app" for Terminal, when it does for the focus assist one. Terminal isn't a UWP, but it does use XAML and I'd imagine that JAWS would still detect the Terminal as a uwp-like app with UWP-like UIA support.

Does this still happen on recent builds? We've gone through a few WinUI updates and the settings UI has been entirely redesigned.

@zadjii-msft commented on GitHub (Aug 23, 2022): This does feel like something that JAWS might have to fix. Curious that it doesn't mention "UWP app" for Terminal, when it does for the focus assist one. Terminal isn't a UWP, but it does use XAML and I'd imagine that JAWS would still detect the Terminal as a uwp-like app with UWP-like UIA support. Does this still happen on recent builds? We've gone through a few WinUI updates and the settings UI has been entirely redesigned.
claunia commented 2026-01-31 05:02:39 +00:00
Author
Owner
Copy Link

@akash07k commented on GitHub (Aug 23, 2022):

@zadjii-msft JAWS works somewhat better with recent builds of WT.
I've tried it last week and it was good so far.

@akash07k commented on GitHub (Aug 23, 2022): @zadjii-msft JAWS works somewhat better with recent builds of WT. I've tried it last week and it was good so far.
claunia commented 2026-01-31 05:02:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 24, 2022):

@zadjii-msft @akash07k JAWS Virtual PC Cursor mode does not work my side on Terminal Preview Version: 1.15.2003.0 as result I am not able to read non-focusable item like Terminal Version number etc.

@ghost commented on GitHub (Aug 24, 2022): @zadjii-msft @akash07k JAWS Virtual PC Cursor mode does not work my side on Terminal Preview Version: 1.15.2003.0 as result I am not able to read non-focusable item like Terminal Version number etc.
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 A11yUsable Area-Accessibility Area-TerminalControl HCL-E+D HCL-WindowsTerminal Issue-Bug 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#16281
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?