Terminal WPF control doesn't support screen readers #16951

Closed
opened 2026-01-31 05:28:18 +00:00 by claunia · 3 comments
Owner

Originally created by @javierdlg on GitHub (Mar 8, 2022).

Originally assigned to: @carlos-zamora on GitHub.

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19043.0

Other Software

Microsoft Visual Studio 2019 and 2022

Steps to reproduce

  1. Turn on Narrator or any other screen reader
  2. Open the WPF Control Test project under the Terminal repo
  3. Write any command and press enter

Expected Behavior

Screen readers read the console output

Actual Behavior

Screen readers ignore the output and only read the written letters

Originally created by @javierdlg on GitHub (Mar 8, 2022). Originally assigned to: @carlos-zamora on GitHub. ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19043.0 ### Other Software Microsoft Visual Studio 2019 and 2022 ### Steps to reproduce 1. Turn on Narrator or any other screen reader 2. Open the WPF Control Test project under the Terminal repo 3. Write any command and press enter ### Expected Behavior Screen readers read the console output ### Actual Behavior Screen readers ignore the output and only read the written letters
Author
Owner

@javierdlg commented on GitHub (Mar 8, 2022):

Added details:
The WPF terminal control doesn't seem to have anything regarding UIA events. It would need some kind of UiaEventDispatcher defined and hooked up to alert the screen reader of new output. Leveraging the NotifyNewOutput() API, would probably be the easiest and fastest way to approach this, because we would force screen readers to read new output. The user can then use the aforementioned hooked up UIA tree to navigate the text buffer as they wish.

@javierdlg commented on GitHub (Mar 8, 2022): Added details: The WPF terminal control doesn't seem to have anything regarding UIA events. It would need some kind of [UiaEventDispatcher](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fblob%2Fmain%2Fsrc%2Ftypes%2FIUiaEventDispatcher.h&data=04%7C01%7Cjadelaga%40microsoft.com%7Cc7a3a2bb2a47469c645408d9fe281a36%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637820270476114176%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7HW5yHevSqWrw%2Fb1SYvmA1W3Wxwh6eSkqF0iuIfUopg%3D&reserved=0) defined and hooked up to alert the screen reader of new output. Leveraging the NotifyNewOutput() API, would probably be the easiest and fastest way to approach this, because we would force screen readers to read new output. The user can then use the aforementioned hooked up UIA tree to navigate the text buffer as they wish.
Author
Owner

@ghost commented on GitHub (Oct 18, 2022):

:tada:This issue was addressed in #14097, which has now been successfully released as Windows Terminal v1.15.2874.🎉

Handy links:

@ghost commented on GitHub (Oct 18, 2022): :tada:This issue was addressed in #14097, which has now been successfully released as `Windows Terminal v1.15.2874`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.2874) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Dec 14, 2022):

:tada:This issue was addressed in #14097, which has now been successfully released as Windows Terminal Preview v1.16.3463.0 and v1.16.3464.0.🎉

Handy links:

@ghost commented on GitHub (Dec 14, 2022): :tada:This issue was addressed in #14097, which has now been successfully released as `Windows Terminal Preview v1.16.3463.0 and v1.16.3464.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.16.3464.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16951