Accessing keystrokes not found within input gestures

[James AUSTIN]

Hi folks

Given  that NVDA is open source, is there a way to access and alter keyboard shortcuts  that do  not appear within the input gestures dialog. I've looked in the user config folder and have found a text file showing some of the shortcuts  from the input gestures dialog, but nothing further.

Is this possible and if so how can I accomplish it please?

Thank you

Warmest wishes

James 

[Andrew Downie]

James, unless I am mistaken, all NVDA commands are shown in the Input Gestures dialog.  Which ones are you not able to find?

Andrew

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAHTne5Kn1MxZ3y3Lh%2Bkp%3DZoj7Pj_zXtzcUXGREzkBcAGcyTz8A%40mail.gmail.com.

[James AUSTIN]

Andrew,

I’m trying to find commands such as read prior and read next line and change some of the object and navigation commands.

But if you were saying that every command can be found within the input gestures dialogue then I apologise, obviously I have not been looking closely enough.

Warmest wishes

Thank you,

JAMES

Sent from my iPhone

On 6 Dec 2025, at 12:55 am, Andrew Downie <doveta...@gmail.com> wrote:



To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CALBhsT56_O%3DD-TTZSGT6NBT56Vi6-o6Ofs2B0rZpgJoyPcXP6Q%40mail.gmail.com.

[joseph....@gmail.com]

Hi,

A few things to note about input gestures dialog and command definitions in NVDA world:

1. Input gestures dialog is contextual. Just before opening input gestures dialog, NVDA will record everything it can about the app or the control you are working on, including the app name, whether browse mode is engaged, and so on. For example, if you are working on an app with no browse mode support, you won’t find browse mode commands in input gestures dialog. Similarly, if you are working on an app for which an add-on is installed and active, you will find additional commands defined by the add-on (but not all add-ons will report input gestures availability or present command descriptions).
2. Input gestures dialog is sensitive to hardware you are using at a given time. Input gestures dialog will not only show keyboard commands, but also commands assigned to whatever braille display you are using and touch gestures if you have NVDA installed on a touch-capable computer. To see the input gestures dialog in its full glory, you must install NVDA on a touch-capable computer, connect a braille display, and open the dialog while browse mode and one or more add-ons (typically global plugins) are active.
3. Not all commands will have descriptions attached. For a command to show up in input gestures dialog, it must have a description text for it. However, not all commands will have description texts (input help messages) for various reason, one of them being that the input gesture is a command native to an app or Windows operating system. For example, the “next line” command, typically assigned to the down arrow key, won’t show up in input gestures dialog because you do not want to reassign it and there is no description text for it.

Of the items noted, the most important thing to remember is that input gestures dialog is context sensitive.

Cheers,

Joseph

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/4A8051F0-EA82-417D-963E-1ED63E5C24FD%40gmail.com.

[Andrew Downie]

Joseph, thank you for the very eloquent explanation of the input gestures dialog.  I have been caught out by its contextual nature a couple of times.  I had not considered the hardware implications previously.

James, no need to apologise for asking questions.  Asking questions is an important part of the learning process.

Andrew

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/005501dc66e2%24fa1fc3a0%24ee5f4ae0%24%40gmail.com.

[jacob kruger]

While not many of them include this, a couple of the add-ons might implement key bindings that are then still not listed in input gestures, but to modify those, you'd most likely need to edit their python code under the NVDA user-data folders, etc., so really depends on context - which keystrokes are you looking for?

Jacob Kruger
"Resistance is futile...acceptance is versatile..."

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CALBhsT56_O%3DD-TTZSGT6NBT56Vi6-o6Ofs2B0rZpgJoyPcXP6Q%40mail.gmail.com.

[jacob kruger]

James, in input preferences dialogue, shift+tab to the search field and you can filter commands there to make it easier to find the ones you are looking for?

Jacob Kruger
"Resistance is futile...acceptance is versatile..."

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/4A8051F0-EA82-417D-963E-1ED63E5C24FD%40gmail.com.

[Cyrille BOUGOT]

Hi James

Note that object navigation commands are listed in the Input Gestures dialog.

As written by others, there are commands with no description that do not appear in this dialog, e.g. down arrow to move to next line. Though if they have no description and thus cannot be reassigned in the Input Gestures dialog, it is very likely that it is done on purpose. For example, the command to move to next line may pass the gesture to the current application, so that the caret is actually moved, and then speak the current line. If you were able to reassign this command, e.g. to pageDown, the command would not work anymore as expected, since page down would be sent to the application, moving the caret many lines below expected...

If you still want to remap scripts with no descriptions, NVDA Dev & Test Toolbox add-on can help you doing this. This may be useful for example to remap Word shortcuts in specific cases, such as Word GUI language not matching NVDA language. Beware though that using this tool may cause unexpected results if you do not know exactly what you are doing, so use it with caution and at your own risk, or do not use it at all.

It would be better if you told us first exactly which command you want to remap, and with which key, so that we can provide better advices.

Cheers,

Cyrille