[nvda] Re: Automatic reading of webpages
- From: "Mario Percinic" <mario.percinic@xxxxxxxxx>
- To: <nvda@xxxxxxxxxxxxx>
- Date: Wed, 29 Apr 2009 10:25:25 +0200
Hmm, i haven't use ie with nvda lately so much, but with FF i didn't have
any problems so far with nvda. Where ever i left the cursor it would be on
the same place except visited links. if i can't find visited lik the fastest
way for me to find where i left of is to go on the bottom om of the page and
look for previously visited link and i would be on the position in a few
seconds.
----- Original Message -----
From: "Vince Thacker" <vince@xxxxxxxxxxxxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Wednesday, April 29, 2009 4:46 AM
Subject: [nvda] Re: Automatic reading of webpages
Hate to say it, but from what I can actually see, IE is better for
returning to the right place on a previous page than any Firefox-like
browser. I use Flock quite a bit, and it seems to have the same fault, if
that's what it is, as Firefox.
Vince.
----- Original Message -----
From: "James Teh" <jamie@xxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Wednesday, April 29, 2009 1:25 AM
Subject: [nvda] Re: Automatic reading of webpages
On 29/04/2009 11:16 AM, Gene wrote:
A screen-reader should not return to a visited link. It should return
to wherever you left off on a web page. If you are reading an article
and stop at the beginning of a sentence, that is where you should be
returned.
Just to provide some info on this:
Note that a link or button is normally the way of "leaving" an article.
I'm not even certain that a web browser visually returns to the exact
position to which the user scrolled if not returning after following a
link. If it does, it should also fire the appropriate events for
assistive technologies.
A screen reader can try to track this information, but I see two problems
with this:
1. The state will be lost when the screen reader is restarted. This
doesn't make sense if the browser is visually returning to the correct
position.
2. If we track the information by URL, inaccuracy and unreliability can
occur. Many pages can have the same URL with different post data. In
addition, the page might have mutated by the time the user returns, in
which case the remembered position will be incorrect.
This is why I'd much prefer to try to get this information from the
browser. The problem is that there seems to be alot of flakiness in this
regard in browsers.
--
James Teh
Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx
Web site: http://www.jantrid.net/
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
Other related posts: