ah didn't know that one.
thanks for the tip.
On 10/22/2018 2:56 PM, Quentin
I didn't notice whether anyone had mentioned this,
but since it's something not everyone knows about, for the
benefit of anyone reading who wonders how GMail's (or any
site's) built-in keystrokes work with NVDA's single letter
navigation (eg H for heading, E for edit box, etc), the way to
do it is to disable NVDA's single letter navigation. To do
this, press NVDA+SHIFT+SPACEBAR to toggle NVDA's single letter
On Tue, Oct 23, 2018 at 1:43 AM Cohn, Jonathan
I know that
your example of Gmail was just an example, but I generally
find that the built-in keystorkes that Gmail provides are
significantly faster to navigate mail with than using the
screen reader functionality.
Essentially, one can open a thread with "o" close a thread
with "u", browse through the list of threads with "j" and "k"
and navigate individual messages in a thread with "n" and "p".
Of course they also have keystrokes for replying, forwarding,
deleting, archiving, and ignore thread.
On 10/21/18, 5:52 PM, "email@example.com
on behalf of Tony Malykh" <firstname.lastname@example.org on behalf of
I have been noticing lately that many browse mode
sluggish in Google Chrome, especially on large web pages.
Let me try
to explain what I mean with an example.
Suppose I open a large email thread (say 20 replies) in
Google Chrome. If I press H and then K, my cursor is
supposed to find
the next heading, and then find the next link after that
stop there. However, if I press them quickly one after the
the after finding that link the cursor would jump back to
heading as if I had pressed Shift+H afterwards. In other
cursor would frirst find the heading, then jump to the
next link, and
then it would mysteriously jump back to that heading
again, all within
a short time, like within a second. I mentioned H and K
example - it seems that this issue can be reproduced with
two browse mode commands, such as F, E, G, and so on.
Has anyone been aware of this issue? Are there any known
One obvious workaround is for me to wait after every
mode keystroke, but that would make using Chrome too
anoying - I would
have to wait for about a second after pressing any browse
Actually I could reproduce this issue on the other
browsers too -
Firefox and IE, although on a much lesser scale. In both
IE you need to press these keystroeks really quickly
less than 0.1 seconds apart to reproduce it, which
affect anyone. This bug is only bothersome in Chrome.
I'm using the latest NVDA 2018.3.2 and the latest Windows
10. I have a
modern laptop, so this is not an issue of running out of
memory. I don't have too many tabs open and I don't have
Training and Support Manager
check out my song on youtube