starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Incoming text is periodically not read by screen readers #14829

New Issue
Open
opened 2026-01-31 04:20:35 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:20:35 +00:00
Owner
Copy Link

Originally created by @Neurrone on GitHub (Aug 10, 2021).

Originally assigned to: @carlos-zamora on GitHub.

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

Screen readers tested: Narrator, NVDA alpha-23553,3c29f9ad, observed while running in WSL2 Ubuntu in case that is somehow relevant

Steps to reproduce

/CC @codeofdusk per our previous discussion about this, @carlos-zamora

This appears to happen Intermittently, but for me I can fairly reliably reproduce this when I'm using Docker to run the postgres cli tool to interact with a Postgres database.

docker run -it postgres:13.3 psql -h db_host -U db_user

I would execute the following commands:

  1. \c <database> to use a database
  2. \d to describe a table

    Expected Behavior

    Incoming text continues to be reliably read by both NVDA and Narrator

    Actual Behavior

    Even though new text would be written on-screen, both NVDA and Narrator would fail to read it. I am able to use object navigation to manually go upwards in NVDA to read the newly written text, but that's not a practical solution.

    The fact that Narrator is also vulnerable to this makes me suspect a bug in Terminal itself.

    Restarting either screen reader does not fix it.

Originally created by @Neurrone on GitHub (Aug 10, 2021). Originally assigned to: @carlos-zamora on GitHub. ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software Screen readers tested: Narrator, NVDA alpha-23553,3c29f9ad, observed while running in WSL2 Ubuntu in case that is somehow relevant ### Steps to reproduce /CC @codeofdusk per our previous discussion about this, @carlos-zamora This appears to happen Intermittently, but for me I can fairly reliably reproduce this when I'm using Docker to run the postgres cli tool to interact with a Postgres database. ```sh docker run -it postgres:13.3 psql -h db_host -U db_user ``` I would execute the following commands: 1. `\c <database>` to use a database 2. \d <table> to describe a table ### Expected Behavior Incoming text continues to be reliably read by both NVDA and Narrator ### Actual Behavior Even though new text would be written on-screen, both NVDA and Narrator would fail to read it. I am able to use object navigation to manually go upwards in NVDA to read the newly written text, but that's not a practical solution. The fact that Narrator is also vulnerable to this makes me suspect a bug in Terminal itself. Restarting either screen reader does not fix it.
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#14829
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?