I'm particularly interested in this question.
Jaws has now become so bad for SSH access in Putty, the Git bash client and the SSH natively in Bash for Windows that I have had to resorted to having a Linux box in run level 3 beside me in work at all times. This has become particularly bad in Jaws 18.
Noone else seems to have the same kind of trouble but this problem is equally bad on several machines from a dell ultra portable, a custom built desktop to the Microsoft Surface book. All running Windows 10.
Several problems I am encountering are:
1. route Jaws to PC sends the mouse to the bottom of the window instead of to the location of the PC cursor.
Navigation by character in Nano / vi / the command line results in Jaws double echoing characters and losing track entirely.
Echoing of new text to the screen works about once every ten times I use any of the various SSH clients available to me.
The Jaws cursor frequently doesn't read anything in the window.
I'm kind of tairing my hair out about SSH access at the moment. It's become so bad that I have to avoid Jaws for this part of my work day.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Bell, Lance (HSAL)
Sent: Wednesday 1 March 2017 14:28
To: Blind sysadmins list