SSH and JAWS

[adns44]

Windows Terminal version

1.15.221212005

Windows build number

10.0.19045.2364

Other Software

JAWS For Windows 2023

Steps to reproduce

Open an Linux SSH host with OpenSSH client and try to use nano to write or edit any text with multiple pines

Expected Behavior

JAWS reads the correct line by navigating up and down and don't start reading from the top of the window when I edit the text in nano.

Seems that the problem relating to rendering but I'm not an expert in it.

Actual Behavior

JAWS not reading properly current line if navigating up and down and when I start writing, at all pressed chars JAWS start reading entire Window from the top, so in Nano it always says the version, filename and the text starting from the top of the screen.

[zadjii-msft]

Huh, I wonder if nano is being entirely redrawn each frame. That sounds insane, but could be possible. Or maybe it's an artifact of nano + ssh.exe + ConPty causing the Terminal to believe that all the lines were invalidated.

@carlos-zamora might know if we're already tracking something similar.

[carlos-zamora]

Unfortunately, screen reader support for full screen TUI applications is a little thin on the ground. We're doing everything we can to standardize better integration with screen readers. But, as of today in 2023, this may not be easy to fix.

I suggest bringing this up as feedback for your AT provider to see if they can do anything differently to better figure out what changed on the screen and how to better present that.

For some background information, the issue here is that when text is output to the buffer, Terminal tells the screen reader that "something changed". The screen reader must then figure out what changed and announce that. We've added a feature to do better and say exactly what got output (i.e. "the letter a was output"), thus forcing the screen reader to immediately read that. However, this is pretty new and screen readers are investigating how to properly take advantage of that.