Re: [orca-list] Firefox caching

[Mallory van Achterberg <stommepoes stommepoes nl>]

Hi,
At least the being thrown back to the top thing isn't a problem
in JAWS new enough to deal with AJAX.  I don't know anything about
reformatting text... I have to match up what I hear with what I
see while testing every time anyway.  It's difficult if I'm not
the one who built the page, but that's due to CSS making stuff
look different than the source.  Though webvisum helps with
outlines.

A warning about down-arrowing to see new content: some (many) developers
update some other part of the page instead.  They shouldn't, for
lots of people, but many developers don't seem to realise not
everyone sees all the screen all the time.  Especially "growls" and
that sort of thing, or error messages placed in front of forms 
but without a refresh (or even after: Amazon's I miss easily). 
Because of this, I would want (ideally) an announcement every time new 
content is brought on the page. It's only obvious if it's later 
in source from the event.

Not an argument for virtual buffers, just some thoughts.

-Mallory


On Sat, Sep 11, 2010 at 02:36:55PM -0700, Steve Holmes wrote:
> On Sat, Sep 11, 2010 at 03:25:15PM +0100, Isaac Porat wrote:
> > Hi
> >
> > This was the same response to a similar question by somebody else
> > perhaps a year ago.  I am using two screen readers in Windows one
> > commercial and the other free both use caching.  If they struggle
> > with the technique there is no sign of it - the response is snappy!
> > There are possible solutions to the problem you raise for example
> > partial refresh.
> >
> > Of course the reasons for slow response can be other things as
> > outlined in other recent posting but lack of caching is a
> > contributor I suspect not an insignificant one.
>
> I'm in full agreement with what Jared said in his last message.  The
> last thing I want to see in Orca is a virtual buffer for a couple
> reasons.  First of all, the virtual buffers I've seen insist on
> reformatting the text so it has no resembolence to what is shown
> visually on the screen.  Try working with a sighted co-worker and
> relate to each other what is on screen.  I had a hell of a time doing
> that while using Window-Eyes and its virtual buffer; it was almost
> impossible to work together on this.  Especially the notion of
> spiewing links one per line; can't think of anything worse than that!
> And of course my other reason was already stated - dynamic content.
> It is a real hassle to reload that buffer every time you think
> something got updated on the page and most of the time, your review
> position gets thrown back to the top of the page.  When it comes to
> virtual buffers in Orca, "Just say now!"
>
> From the point of view of performance, I doubt virtual buffers would
> help this much.  The page contents are already loaded into the browser
> and if something changes on the page due to some user action, then
> that part will get loaded.  At this point in time, I have seen where
> Orca did not announce the change in content; not sure if there is a
> bug there or if that just isn't happening yet.  But subsequent presses
> of down-arrow will quickly reveal that the page has been updated with
> new stuff.
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp