Mostly designed for use with object navigation (to get you where regular navigation keys like the arrows and tab can't get to), I must confess I haven't
looked at the technicalities of exactly how the behaviour differs, but great that it works as a solution here :)

Hi Glenn, it's been quite a long time.

Yes, it takes you directly to the result, no dialog box.

As others have said, NVDA+control+f is what you want here.

However, since it seems you may have tried that (you said Control+insert+f, but that's the same thing if you have your insert key set as the NVDA key), some debugging steps:

First, do you have "enable browse mode on page load" checked, in the browse mode settings? You can reach the browse mode settings by pressing NVDA+control+b, then tabbing to the option.
If you don't, please check it, then press enter, and again try to do a search with NVDA+control+f.

Can you tell us what browser you are using?

Can you please give an example of a page you go to (so we can go there), and a term you search for to which you expect to be taken but aren't (so we can search for it)?

Luke


On Thu, 8 Apr 2021, Glenn / Lenny wrote:

I use control + F to find something on a web page or document with Jaws just fine, but that never works with NVDA.
I've tried insert + control F too and it does not work.
It seems to act as though it did the search, but it does not place me on the page at what I searched for.
In fact, this has never worked for me, I'm sure even before I ever installed any addons.
I just assumed over the years that maybe NVDA does not do this.
When it does work for someone, does it actually move the reading cursor to the spot, or does it say it found something and leave a dialog box open?
I don't know if NVDA has done that before, or if it was something else, but I'm expecting the reading cursor to go to the first instance of my search, as
Jaws does.

Luke, it's the "activate navigator object" key. Using the laptop
layout, it's NVDA+enter.

On Thu, 8 Apr 2021, Jackie wrote:

NVDA+enter key seems to work quite well, David.

Really? Is that documented somewhere? Now, NVDA+numpad enter, I can
understand,
but the regular one?
Where does that work that just enter might not?

I don't doubt you, I've just never heard of it, and keyboard help has
nothing on
it.

Luke

Hi NVDA,

I share the following link with you in the hope it may be helpful
alongside the NVDA command key list. I will try these at the brokerage
site, webull.com.
This site caters mostly to US residents.

How to Move the Mouse Cursor with the Keyboard in Windows
https://www.computerhope.com › ... › Keyboard Help
About this Result
Using keyboard shortcut — How to enable/disable Mouse Keys. Using
keyboard shortcut; In Windows 10; In Windows 8; In Windows 7, Vista,
or XP.

Thank you for your time and input: Luke, Brian, Gene.


David Russell

My apologies to Gene, Joseph, and Luke.  I read Bob's question, started my reply, walked away, and never reloaded to check to see what might have come between when I walked away and got back.  I've covered territory already covered previously.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

Bob,

          Before I start even trying to explain this, it would be helpful to know what browser or browsers you and Glenn are using and where either one of these finds is not working.

           I am going to try to make the distinction between a browser find and a screen reader find (and it doesn't matter whether it's JAWS or NVDA) as simple as I can.  I can assure you that I will be omitting scads of "under the hood" detail that someone far more knowledgeable about both browser internals and NVDA internals can delve in to if they so choose.

            A browser find focuses on what can be seen on a page that's a part of the page text.  That is generally limited to actual text as well as text used for click-through links and labels.  But text on controls, like buttons, checkboxes, etc., will very often not be found using a browser find.  Much of this depends on how sloppy the page coders have been about how certain controls are written and what's exposed to a browser find versus a screen reader find.  I also believe that a browser find does not examine the virtual cursor used by the screen reader while a screen reader find does just that.

             As a result, there can be differences in not only what can be found by either one, but exactly where the screen reader focus is after each is done.

             I tend to favor the screen reader find when someone's using a screen reader simply because it tends to find certain things that a browser find doesn't, and you more often have focus on the thing just found, consistently, with a screen reader find.

             I'm actually hoping someone with way more "under the hood" knowledge will chime in and probably bore some of us silly getting into the actual differences between how a browser find and screen reader find works and can explain the discrepancies not only in what each can find but in where focus lies after each.  I have never been able to come up with any precise way of describing what's different between the two.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

On Thu, Apr 8, 2021 at 09:52 PM, Gene wrote:

Control f is not the find command for NVDA. its control NVDA key f.

-
Indeed, but it appears the questioner has described using browser find
(CTRL+F) and NVDA Find (NVDA+CTRL+F) and neither is working as expected.
Why that would be, I cannot say, since browser find or NVDA find both work
for me (and many others) when either is used, depending on what, exactly one
is trying to do.

I have suggested trying: The Most Basic Troubleshooting Steps for Suspected
NVDA Issues ( https://nvda.groups.io/g/nvda/message/81494 )
as a starting point.

--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042

Always remember others may hate you but those who hate you don't win unless
you hate them. And then you destroy yourself.

~ Richard M. Nixon

Perhaps I should have explained better. My method was as follows:
Control+Alt+N to restart NVDA.
When that didn't work, I switched windows a few times, then in an
attempt to get things to work as expected, started closing Firefox
windows. It was around this time I thought my computer had frozen
which it has had a tendency to do lately, but before I decided to hard
reboot, I fired up Narrator and discovered that pressing Alt+F4 had in
fact been closing windows as expected, but NVDA must have crashed as
it quit speaking.

On 4/8/21, Luke Davis <luke@...> wrote:

On Thu, 8 Apr 2021, Bob Cavanaugh wrote:

around for a few minutes then crashed. I was only made aware of this
by firing up Narrator and discovering that I had been closing Firefox
windows all along.

Can you explain that more? To my knowledge, the key sequence to close
NVDA,
is
quite dissimilar to the one for closing Firefox windows.
I find your lack of specificity disturbing. :)

Luke

I use control + F to find something on a web page or document with Jaws just fine, but that never works with NVDA.
I've tried insert + control F too and it does not work.
It seems to act as though it did the search, but it does not place me on the page at what I searched for.
In fact, this has never worked for me, I'm sure even before I ever installed any addons.
I just assumed over the years that maybe NVDA does not do this.
When it does work for someone, does it actually move the reading cursor to the spot, or does it say it found something and leave a dialog box open?
I don't know if NVDA has done that before, or if it was something else, but I'm expecting the reading cursor to go to the first instance of my search, as
Jaws does.

On Thu, Apr 8, 2021 at 09:52 PM, Gene wrote:

Control f is not the find command for NVDA. its control NVDA key f.

-
Indeed, but it appears the questioner has described using browser find
(CTRL+F) and NVDA Find (NVDA+CTRL+F) and neither is working as expected.
Why that would be, I cannot say, since browser find or NVDA find both
work for me (and many others) when either is used, depending on what,
exactly one is trying to do.

I have suggested trying: The Most Basic Troubleshooting Steps for
Suspected NVDA Issues ( https://nvda.groups.io/g/nvda/message/81494 )
as a starting point.

--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042

Always remember others may hate you but those who hate you don't win
unless you hate them. And then you destroy yourself.

~ Richard M. Nixon

On Thu, Apr 8, 2021 at 09:52 PM, Gene wrote:

Control f is not the find command for NVDA. its control NVDA key f.

-
Indeed, but it appears the questioner has described using browser find
(CTRL+F) and NVDA Find (NVDA+CTRL+F) and neither is working as expected.
Why that would be, I cannot say, since browser find or NVDA find both work
for me (and many others) when either is used, depending on what, exactly one
is trying to do.

I have suggested trying: The Most Basic Troubleshooting Steps for Suspected
NVDA Issues ( https://nvda.groups.io/g/nvda/message/81494 )
as a starting point.

--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042

Always remember others may hate you but those who hate you don't win unless
you hate them. And then you destroy yourself.

~ Richard M. Nixon