Differences between using the NVDA and the browser commands search on a webpage


 

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook


Gene
 

You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene

Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook


 

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:

You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook



Gene
 

If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene

----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook



 

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:

If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Gene
 

The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene

----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




 

Ok, I got it now. Thanks for the answers :)
Em 24/02/2019 15:05, Gene escreveu:

The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook





Brian's Mail list account <bglists@...>
 

Yes the problem is unless you refresh the page after a web side search, nothing has changed as the old buffer is still in memory.
This is also why sometimes nvda still says that a page is displayed when its changed if it missed the update page signal, and one has to force it to reload.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, February 24, 2019 5:11 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage


You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use. You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader. You must use the search command the screen-reader designates.

Gene
From: marcio via Groups.Io
Sent: Sunday, February 24, 2019 10:09 AM
To: nvda@nvda.groups.io
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage


Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.


--

Cheers,
Marcio
Follow or add me on Facebook


Brian's Mail list account <bglists@...>
 

One assumes it highlights the area without actually changing the page.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "marcio via Groups.Io" <marcinhorj21=yahoo.com.br@groups.io>
To: <nvda@nvda.groups.io>
Sent: Sunday, February 24, 2019 5:13 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage


But, what's the point of the "search for" option built-in on the
browser? How one would deal with this option not using a screen reader?

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>

Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use
browse mode or the Virtual PC cursor use. You aren't working directly
with the page in browse mode or equivalent mode in a different
screen-reader. You must use the search command the screen-reader
designates.
Gene
*From:* marcio via Groups.Io <mailto:marcinhorj21=yahoo.com.br@groups.io>
*Sent:* Sunday, February 24, 2019 10:09 AM
*To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject:* [nvda] Differences between using the NVDA and the browser
commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing
happens after I hit enter. On the other hand if I use the NVDA command
I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook <https://facebook.com/firirinfonfon>




Travis Siegel <tsiegel@...>
 

I don't know specifically about firefox, but in chrome, notepad, and other windows programs (which would presumably include firefox as well), after you hit control-F for find, type in your text, and press enter, you then need to press escape, and it will put you at the spot where the text was found.  The nice thing about this is that if you want to search agai, most of the time, just pressing F3 will repeat the search, and place your cursor at the appropriate spot without you having to do anything else.  I have rarely used the NVDA specific search capability, only a time or two when the web pages weren't cooperating because of javascript, scrolling text and the like.

On 2/24/2019 11:09 AM, marcio via Groups.Io wrote:
Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook


Virus-free. www.avast.com


Travis Siegel <tsiegel@...>
 

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Gene
 

That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----

Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Travis Siegel <tsiegel@...>
 

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Gene
 

If you search using a browser or a PDF reader that supports browse mode, you have to use the NVDA find command.  The Windows program command won't work.  Since the thread is about the NVDA find command in browse mode, this needs to be clearly stated to avoid confusion. 
 
Gene

----- Original message -----
Sent: Monday, February 25, 2019 8:53 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Travis Siegel <tsiegel@...>
 

I think we're having a difference of terms here. 

The default mode for NVDA in a web browser is of course browse mode.  If you enter on a form element, it then switches into forms mode.  Switching out of this forms mode puts you back into browse mode.  Feel free to correcxt me if I'm wrong, but that is my experience, and also what the documentation claims, so with that said.

I will repeat my assertion that control-F works just fine when I'm in Chrome, and I want to find something on the page.  I simply hit control-F, type in what I'm looking for, and my cursor is moved to the point where that text appears.  If I want to search for the same text again, I simply press F3, and I'm moved to the next occurrence of the text.  I need not use NVDA specific commands to get this behavior, the standard windows find command works just fine, and always has for me.

If you're talking about something else, then please enlighten me, because I don't know of any other way to look at screen content.

On 2/25/2019 10:20 PM, Gene wrote:
If you search using a browser or a PDF reader that supports browse mode, you have to use the NVDA find command.  The Windows program command won't work.  Since the thread is about the NVDA find command in browse mode, this needs to be clearly stated to avoid confusion. 
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 8:53 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Rosemarie Chavarria
 

Hi, Travis,


When I shopped on the Albertsons site years ago, I used to use control F to find a link for what I wanted. For instance, I wanted to buy chicken pot pies so I hit control F and typed "pot pies" without the quotes. I then hit escape and the link for pot pies came up. All I had to do was hit enter on it and I could browse through the pot pies to find the chicken ones.


Rosemarie



On 2/25/2019 7:31 PM, Travis Siegel wrote:

I think we're having a difference of terms here. 

The default mode for NVDA in a web browser is of course browse mode.  If you enter on a form element, it then switches into forms mode.  Switching out of this forms mode puts you back into browse mode.  Feel free to correcxt me if I'm wrong, but that is my experience, and also what the documentation claims, so with that said.

I will repeat my assertion that control-F works just fine when I'm in Chrome, and I want to find something on the page.  I simply hit control-F, type in what I'm looking for, and my cursor is moved to the point where that text appears.  If I want to search for the same text again, I simply press F3, and I'm moved to the next occurrence of the text.  I need not use NVDA specific commands to get this behavior, the standard windows find command works just fine, and always has for me.

If you're talking about something else, then please enlighten me, because I don't know of any other way to look at screen content.

On 2/25/2019 10:20 PM, Gene wrote:
If you search using a browser or a PDF reader that supports browse mode, you have to use the NVDA find command.  The Windows program command won't work.  Since the thread is about the NVDA find command in browse mode, this needs to be clearly stated to avoid confusion. 
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 8:53 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Gene
 

Are you talking about when you have gone into forms mode or when you are working in browse mode.  See the manual if you are talking about browse mode.  The commands I've given are specified and control f doesn't work when in browse mode which, as I recall, is specified in the manual.  Blind people wouldn't use find in forms mode because they can't navigate around the page in that way so if it works, it is impractical.
 
Gene

----- Original message -----
Sent: Monday, February 25, 2019 9:31 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I think we're having a difference of terms here. 

The default mode for NVDA in a web browser is of course browse mode.  If you enter on a form element, it then switches into forms mode.  Switching out of this forms mode puts you back into browse mode.  Feel free to correcxt me if I'm wrong, but that is my experience, and also what the documentation claims, so with that said.

I will repeat my assertion that control-F works just fine when I'm in Chrome, and I want to find something on the page.  I simply hit control-F, type in what I'm looking for, and my cursor is moved to the point where that text appears.  If I want to search for the same text again, I simply press F3, and I'm moved to the next occurrence of the text.  I need not use NVDA specific commands to get this behavior, the standard windows find command works just fine, and always has for me.

If you're talking about something else, then please enlighten me, because I don't know of any other way to look at screen content.

On 2/25/2019 10:20 PM, Gene wrote:
If you search using a browser or a PDF reader that supports browse mode, you have to use the NVDA find command.  The Windows program command won't work.  Since the thread is about the NVDA find command in browse mode, this needs to be clearly stated to avoid confusion. 
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 8:53 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


 

Travis and Gene,

         This is actually very complicated, and both of you are correct and incorrect, depending on the context.

          Travis, once NVDA is up bring up the NVDA menu and from there the Commands Quick Reference, which opens in your default web browser, which in my case is Chrome.  Now try using straight CTRL+F to find anything and have NVDA speak it.  I certainly can't get it to work.  On that page I have to use NVDA find to get the behavior I'd expect as far as the screen reader giving me feedback, otherwise I get NADA.

          I have had times where regular find works fine, but they are sporadic and inconsistent, thus I always encourage my clients (whether using JAWS or NVDA) to use the screen reader find.

          If I had to come down on "best practice" here it is to follow Gene's advice and use a screen reader find if you want consistent feedback from the screen reader in regard to what it's found and whether what it's found is part of a control of some sort or just in the flow of text on a page.

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 


Gene
 

Rosemary
 
Were you using JAWS or NVDA at that time.  JAWS has made control f the find command in the virtual pc cursor.  But you aren't using the browser's find command.  JAWS uses control f for its own virtual PC cursor find command and JAWS intercepts control f and keeps it from reaching the browser.
 
It is important that people know that NVDA has its own find commands while in browse mode.  Over the years, I've seen many times when new NVDA users have asked how to search and have said that control f doesn't work.
 
Gene

----- Original Message -----
From: Gene
Sent: Monday, February 25, 2019 9:41 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Are you talking about when you have gone into forms mode or when you are working in browse mode.  See the manual if you are talking about browse mode.  The commands I've given are specified and control f doesn't work when in browse mode which, as I recall, is specified in the manual.  Blind people wouldn't use find in forms mode because they can't navigate around the page in that way so if it works, it is impractical.
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 9:31 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I think we're having a difference of terms here. 

The default mode for NVDA in a web browser is of course browse mode.  If you enter on a form element, it then switches into forms mode.  Switching out of this forms mode puts you back into browse mode.  Feel free to correcxt me if I'm wrong, but that is my experience, and also what the documentation claims, so with that said.

I will repeat my assertion that control-F works just fine when I'm in Chrome, and I want to find something on the page.  I simply hit control-F, type in what I'm looking for, and my cursor is moved to the point where that text appears.  If I want to search for the same text again, I simply press F3, and I'm moved to the next occurrence of the text.  I need not use NVDA specific commands to get this behavior, the standard windows find command works just fine, and always has for me.

If you're talking about something else, then please enlighten me, because I don't know of any other way to look at screen content.

On 2/25/2019 10:20 PM, Gene wrote:
If you search using a browser or a PDF reader that supports browse mode, you have to use the NVDA find command.  The Windows program command won't work.  Since the thread is about the NVDA find command in browse mode, this needs to be clearly stated to avoid confusion. 
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 8:53 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com


Rosemarie Chavarria
 

I was using Jaws at that time.



On 2/25/2019 7:45 PM, Gene wrote:
Rosemary
 
Were you using JAWS or NVDA at that time.  JAWS has made control f the find command in the virtual pc cursor.  But you aren't using the browser's find command.  JAWS uses control f for its own virtual PC cursor find command and JAWS intercepts control f and keeps it from reaching the browser.
 
It is important that people know that NVDA has its own find commands while in browse mode.  Over the years, I've seen many times when new NVDA users have asked how to search and have said that control f doesn't work.
 
Gene
----- Original Message -----
From: Gene
Sent: Monday, February 25, 2019 9:41 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Are you talking about when you have gone into forms mode or when you are working in browse mode.  See the manual if you are talking about browse mode.  The commands I've given are specified and control f doesn't work when in browse mode which, as I recall, is specified in the manual.  Blind people wouldn't use find in forms mode because they can't navigate around the page in that way so if it works, it is impractical.
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 9:31 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I think we're having a difference of terms here. 

The default mode for NVDA in a web browser is of course browse mode.  If you enter on a form element, it then switches into forms mode.  Switching out of this forms mode puts you back into browse mode.  Feel free to correcxt me if I'm wrong, but that is my experience, and also what the documentation claims, so with that said.

I will repeat my assertion that control-F works just fine when I'm in Chrome, and I want to find something on the page.  I simply hit control-F, type in what I'm looking for, and my cursor is moved to the point where that text appears.  If I want to search for the same text again, I simply press F3, and I'm moved to the next occurrence of the text.  I need not use NVDA specific commands to get this behavior, the standard windows find command works just fine, and always has for me.

If you're talking about something else, then please enlighten me, because I don't know of any other way to look at screen content.

On 2/25/2019 10:20 PM, Gene wrote:
If you search using a browser or a PDF reader that supports browse mode, you have to use the NVDA find command.  The Windows program command won't work.  Since the thread is about the NVDA find command in browse mode, this needs to be clearly stated to avoid confusion. 
 
Gene
----- Original message -----
Sent: Monday, February 25, 2019 8:53 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

I wasn't talking about the NVDA specific search function, I was talking about the find function that is present in just about every windows program in existence.  A simple control-F will do your initial find, and after that, simply pressing F3 will repeat the find command from the current position of the regular cursor.  I almost never find it useful or necessary to use the NVDA specific find function.  As I said, I've only had to use it a handful of times. 

I always use the standard windows find function and it almost always works for me with little to no issues.  And, it's fewer keystrokes, so it saves me lots of time as well.


On 2/25/2019 9:39 PM, Gene wrote:
That isn't correct.  In NVDA, to search when in browse mode, the command is either insert and control. while holding those keys, type f to open the search dialog.  Repeat search is either insert and f3.

Gene
----- Original Message -----
Sent: Monday, February 25, 2019 8:07 PM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

The screen reader works just fine with the text of the web page.  I use control-f all the time to search for things, and it always works, except when the page is loaded with javascript that yanks the focus away from the main cursor.  Any normal web page works just fine with the ergular find command.  As I said before, I've only ever used the NVDA find command a couple times.  Of course, for the most part, it's not really necessary to search for things on the web page if you use your navigation commands to get from here to there in web browsers.

On 2/24/2019 1:05 PM, Gene wrote:
The screen-reader can't work with the search built into the browser.  The page that you are reading is in a buffer where the screen-reader reformats it.
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:30 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

So it's an option that the screen reader isn't able to deal with, is it right?
Sorry for asking too much as I am but it really got me curious.
Em 24/02/2019 14:30, Gene escreveu:
If you aren't using a screen-reader you use the actual search built into the browser itself. 
 
Gene
----- Original Message -----
Sent: Sunday, February 24, 2019 11:13 AM
Subject: Re: [nvda] Differences between using the NVDA and the browser commands search on a webpage

But, what's the point of the "search for" option built-in on the browser? How one would deal with this option not using a screen reader?
Em 24/02/2019 14:11, Gene escreveu:
You are searching using the buffer which screen-readers that use browse mode or the Virtual PC cursor use.  You aren't working directly with the page in browse mode or equivalent mode in a different screen-reader.  You must use the search command the screen-reader designates.
 
Gene
Sent: Sunday, February 24, 2019 10:09 AM
Subject: [nvda] Differences between using the NVDA and the browser commands search on a webpage

Hi guys,
Anyone could tell me what's the difference between these two commands?
I'm asking because using the browser command to search, nothing happens after I hit enter. On the other hand if I use the NVDA command I'll able to search for what I'm wanting to.
P.S.: Using Firefox.

--

Cheers,
Marcio
Follow or add me on Facebook




Virus-free. www.avast.com