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

JAWS is not narrating the output information generated in terminal window. #21082

New Issue
Closed
opened 2026-01-31 07:32:40 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:32:40 +00:00
Owner
Copy Link

Originally created by @Saiteja341 on GitHub (Jan 9, 2024).

Originally assigned to: @DHowett, @carlos-zamora on GitHub.

Windows Terminal version

1.18.3181.0

Windows build number

26020.1000

Other Software

Test Environment:
OS: Windows 11 Version 23H2 (OS Build 26020.1000)
App: Windows Terminal Preview
Screen Reader: Jaws

Steps to reproduce

1.Open Windows Terminal.
2.Turn on Jaws.
3.Now give any command Ex: Hostname & press enter.
4.output will be generated in the window.
5.Observe whether screen reader is narrating the output information or not.

Observation with NVDA & Narrator:
Issue don't repro with NVDA & Narrator.

User Experience:
People with visual impairments who rely on the screen readers will not know the information of generated output, if screen reader don't narrate the output information.

Guideline link:
https://www.w3.org/TR/WCAG21/#info-and-relationships

Attachment:
JAWS is not narrating output information..zip

Expected Behavior

Screen reader should narrate the output information upon pressing enter after giving the command.

Actual Behavior

Screen reader is staying silent & not narrating any information regarding the output generated in the window.

Originally created by @Saiteja341 on GitHub (Jan 9, 2024). Originally assigned to: @DHowett, @carlos-zamora on GitHub. ### Windows Terminal version 1.18.3181.0 ### Windows build number 26020.1000 ### Other Software Test Environment: OS: Windows 11 Version 23H2 (OS Build 26020.1000) App: Windows Terminal Preview Screen Reader: Jaws ### Steps to reproduce 1.Open Windows Terminal. 2.Turn on Jaws. 3.Now give any command Ex: Hostname & press enter. 4.output will be generated in the window. 5.Observe whether screen reader is narrating the output information or not. Observation with NVDA & Narrator: Issue don't repro with NVDA & Narrator. User Experience: People with visual impairments who rely on the screen readers will not know the information of generated output, if screen reader don't narrate the output information. Guideline link: https://www.w3.org/TR/WCAG21/#info-and-relationships Attachment: [JAWS is not narrating output information..zip](https://github.com/microsoft/terminal/files/13872541/JAWS.is.not.narrating.output.information.zip) ### Expected Behavior Screen reader should narrate the output information upon pressing enter after giving the command. ### Actual Behavior Screen reader is staying silent & not narrating any information regarding the output generated in the window.
claunia commented 2026-01-31 07:32:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 9, 2024):

@carlos-zamora Any idea if we were tracking this before? This sounds familiar, but also, I'm not sure what we would have done to break JAWS

@zadjii-msft commented on GitHub (Jan 9, 2024): @carlos-zamora Any idea if we were tracking this before? This sounds familiar, but also, I'm not sure what we would have done to break JAWS
claunia commented 2026-01-31 07:32:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 31, 2024):

@Saiteja341 Which version of JAWS are you using? IIRC this was fixed in an earlier version of JAWS, but if it's regressed, that would be good to know!

@zadjii-msft commented on GitHub (Jan 31, 2024): @Saiteja341 Which version of JAWS are you using? IIRC this was fixed in an earlier version of JAWS, but if it's regressed, that would be good to know!
claunia commented 2026-01-31 07:32:42 +00:00
Author
Owner
Copy Link

@Bekreth commented on GitHub (Mar 19, 2024):

I'm having this issue as well. I've been building a CLI for a user that uses JAWS and everything was working fine with Windows 10/JAWS 2022. We just upgraded their machine and JAWS now only reads out key strokes and nothing that is printed to the terminal. Our system versions are as listed below:

JAWS version : 2024.2312.53
Windows version : 22H2 22621.3007

Is it known yet whether this issue stems from JAWS or from the Window?

@Bekreth commented on GitHub (Mar 19, 2024): I'm having this issue as well. I've been building a CLI for a user that uses JAWS and everything was working fine with Windows 10/JAWS 2022. We just upgraded their machine and JAWS now only reads out key strokes and nothing that is printed to the terminal. Our system versions are as listed below: JAWS version : 2024.2312.53 Windows version : 22H2 22621.3007 Is it known yet whether this issue stems from JAWS or from the Window?
claunia commented 2026-01-31 07:32:42 +00:00
Author
Owner
Copy Link

@Bekreth commented on GitHub (Mar 19, 2024):

I was able to solve this problem upgrading JAWS to 2024.2403.3

@Bekreth commented on GitHub (Mar 19, 2024): I was able to solve this problem upgrading JAWS to 2024.2403.3
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 A11yUsable HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix Priority-1 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#21082
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?