Re: Find On Page
JAWS reassigns that command to work with the virtual pc cursor. Window-eyes didn't use control f either. it used Control shift f.toggle quoted messageShow quoted text
Browsers have their own find command, usually control f. But the virtual PC cursor or browse mode is not using the browser find command because when you move through a page using the virtual pc cursor or browse mode, you are using a virtual cursor, there is no cursor on the actual page. A sighted person looks at the page and reads what is there. He doesn't move through a page with a cursor. He can scroll down, causing new text to appear on the screen, but there is no cursor. You don't need a cursor if you are just reading and aren't intended to edit anything. The reason you can move around a web page as though you were in a word processor is because the screen-reader simulates a cursor. If it didn't, you couldn't properly move in a web page to read what you want and skip what you want.
When you use the browser's find command, you are telling the virtual cursor to move to the find result.
From: Bob Cavanaugh
Sent: Thursday, April 08, 2021 9:52 PM
Subject: Re: [nvda] Find On Page
What is the difference between browser find and NVDA find? It seems
odd to me that control+F does not work in NVDA as expected when I've
had no issues with it in any other screen reader. I would suggest a
change here, but I have no idea what would need to be changed.
On 4/8/21, Brian Vogel <firstname.lastname@example.org> wrote:
On Thu, Apr 8, 2021 at 09:52 PM, Gene wrote:-