Re: NVDA documentation
|
David Mellor
Thanks Gene.
I
didn't know NVDA-b would select the object when stopped like
that.
The facility to browse through the objects manually allows more
careful consideration though. :)
David
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene Sent: 09 September 2021 14:17 To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA documentation I meant NVDA b. I’m not sure if that is the same thing as is being
discussed but, if you are in object review, using that command moves through
every object in the active window. And if you stop when a certain object
is being announced the object navigator will be on that object.
Gene
-----Original Message-----
From: David Mellor
Sent: Thursday, September 09, 2021 8:06 AM
Subject: Re: [nvda] NVDA documentation NVDA+2 (main keyboard) toggles speaking of typed
characters?
I'm not sure what you had in mind there Gene.
David
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene Sent: 09 September 2021 13:25 To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA documentation Is scrolling through all the objects the same thing as using NVDA key 2 on
the main keyboard?
Gene
-----Original Message-----
From: David Mellor
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation Hi Quentin , I'm not too concerned with arguing the case for default key strokes being setup. So long as it goes into the manual then people can set the keys up if they wish. I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects. I have certainly used this on occasion. I've assigned them to 3 and 9, prev and next respectively. Very best wishes, David
|
|
|