There is no script for PuTTY. It was previously necessary to modify the say nonhighlighted text function or add this to the PuTTY script but since Jaws 18 that's no longer necessary. However, this never helped cursor tracking and often resulted in too much text being spoken. It was workable though. Creating scripts for this is beyond my scripting knowledge. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of John G Heim Sent: Wednesday 1 March 2017 15:47 To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Suggestions for other SSH Clients You might be able to fix the jaws script for putty though. I haven't been a Windows user for many years now but the jaws scripting list used to be very active and very helpful. If someone wants to perform a valuable service for the blind community, you could write a jaws script for putty. Don't look at me, I am a linux user. On 03/01/2017 08:51 AM, Darragh Ó Héiligh wrote:
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 <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Suggestions for other SSH Clients
Hi all and thanks for the thought Dave. Does anyone have any suggestions as to their most favourite SSH Client and how effective screen readers work with that software.
Best regards, Lance
-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of David Mehler Sent: February-28-17 11:44 AM To: blind-sysadmins Subject: [Blind-sysadmins] Bitvise ssh client
Hello,
If anyone is using bitvise ssh client with a screen reader please let me know. I'd like to know which one and what you had to do to make it work?
Thanks. Dave.
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins