Re: speaking commands

Jonathan COHN

That was a nice feature of WindowEyes, one could create side effects for keys bound to a function, so that either prior to or after the primary function ran, other events could occur including speaking or routing focus to the best place. This was a menu driven type system, that required no programming skills to implement.



From: <>
Date: Wednesday, June 24, 2020 at 10:19 AM
To: <>
Subject: Re: [nvda] speaking commands

External email alert: Be wary of links & attachments.

And, it is not so difficult to implement my suggestion:

1 - Typable keys, including letters, numbers, accents, like accut, grabv, tilde, circunflex, diaresis and so on, and enter;

2 - Arrow keys;

3 - Command keys, all other keys.


After that, close all tickets about this.

If after that, someone reopens or create new tickets, the solution can be evaluated again...


Rui Fontes

NVDA portuguese team



Às 15:05 de 24/06/2020, David Griffith escreveu:


I agree absolutely – it never made any sense at all to me that people who needed assistance with locating control keys would inevitably also have similar problems locating and using the routine cursor keys.

It seemed a bizarre design assumption from the  first to compel noisy feedback from every push of a cursor key if you wanted to  avail yourself of reassurance with the use of a control key like alt or control etc.

David Griffith

David Griffith



Sent from Mail for Windows 10


From: Rui Fontes
Sent: 24 June 2020 01:28
Subject: Re: [nvda] speaking commands




Have you seen the implementation made by paulber in his add-on NVDAExtensionGlobalPlugin?


I have already gave suggestions in this issue.

Reading the issue, most people agree that arrow keys should be treated differently from other command keys...


And one of my suggestions have benn backed up by two or three other participants in the issue...




Rui Fontes

NVDA portuguese team


Rui Fontes

NVDA portuguese team



Às 00:17 de 24/06/2020, Quentin Christensen escreveu:



There has been discussion on this:


Much of the issue is that everyone has different ideas on the best way forward for this.  If anyone has new ideas, then do, please comment on that issue.




On Tue, Jun 23, 2020 at 9:12 PM Rui Fontes <rui.fontes@...> wrote:

Quentin, have you already tried to work with NVDA in those conditions?


NVDA needs, urgently, a way to filter some keypresses from being announced...


See issues #5484, #5608 and many more..


Rui Fontes



Às 04:34 de 23/06/2020, Quentin Christensen escreveu:

If you press NVDA+4, or toggle "Speak command keys" in NVDA's keyboard settings, it will speak keys such as ENTER or CONTROL+S.


NVDA doesn't automatically know that CONTROL+S is save, so it generally won't automatically announce that, however if the keystroke brings up something like a save dialog, then that would be announced (for instance the first time you press control+s in a new document in Word).


Not directly related to control+s, but there is a "clipspeak" add-on which will report the functions of some keys such as control+c (Copy) and control+v (paste) where they perform those functions:


Kind regards




On Tue, Jun 23, 2020 at 12:17 PM Grant Metcalf <the.gems@...> wrote:

I am hoping that sometime soon the NVDA developers will have NVDA speak commands such as “control-save”. I am always in doubt if I have been able to save the file I am working on. Mostly I use the text editor Notepad and very occasionally Wordpad for “RTF” files. Granpa DOS would appreciate all efforts the developers would exert toward making the very basic commands speak!

Cordially yours.


Listening for HIS shout!

Grant Metcalf





Quentin Christensen
Training and Support Manager





Quentin Christensen
Training and Support Manager



Join to automatically receive all group messages.