Amen, Travis. I couldn't have said it any better.
toggle quoted messageShow quoted text
On 2/25/2019 7:51 PM, Travis Siegel
wrote:
Oh for god's sake man, read the message you're replying to
before asking questions that are already answered in the text
you're replying to.
This is getting ridiculous.
Obviously, forms mode isn't going to let me search for
anything, because forms mode is an input mode, not a look around
the page and see what's there mode.
Control-F (which is the standard windows find function), works
in browse mode. If you're telling me that it doesn't work in
browse mode, then I'm telling you that your understanding is
incorrect. Go ahead, open your favorite browser, and give it a
try. I think you'll find it works just fine.
On 2/25/2019 10:41 PM, Gene wrote:
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.
|
