Re: [orca-list] Why flat review was causing focus losses in GNOME 3.9.x

[Alex Midence <alex midence gmail com>]

Hi,

A bit confused here.  Is the answer to this feature suggestion, wait till
the toolkit developers of qt, gtk, gecko, ETC. fix stuff on their end
(whenever that may be) and then, Orca will be in a position to implement
this feature?  Otherwise, it won't exist?  Orca can't generate this feature
on its own?  Incidentally, someone asked if Windows screen readers have a
way to track their analogous version of flat review and the answer is yes,
somewhat.  I understand NVDA can manage this but, Jaws often has a hard time
with it.  You have to tether the simulated mouse cursor to the flat review
cursor so people can see what you are doing.  Otherwise, it's hard
especially in stuff like the virtual viewer or, I think the equivalent word
is the virtual buffer?  Stuff where the regular cursor is being used as is
the case in Microsoft Office applications with the exception of Powerpoint,
a sighted person can follow you just fine.  In powerpoint which uses a
virtual buffer to represent the slide you are looking at in the slide show,
they can't tell where you are reading unless you tell them where you are.
As for the tethering the mouse pointer to the pc cursor or virtual cursor,
this causes problems of its own because, in browsers, the main user of
virtual buffers in Windows, you can activate all kinds of elements that have
the "onmouseover" attribute on them which causes nightmares of reading a
page for you if you are not conscious of this behavior.  

Hth,
Alex M




-----Original Message-----
From: orca-list [mailto:orca-list-bounces gnome org] On Behalf Of Luke
Yelavich
Sent: Thursday, September 12, 2013 5:53 PM
To: orca-list gnome org
Subject: Re: [orca-list] Why flat review was causing focus losses in GNOME
3.9.x

On Fri, Sep 13, 2013 at 08:48:04AM EST, Joanmarie Diggs wrote:
> Absolutely. And to do it right what we need is new API which toolkits 
> would implement to highlight the accessible component and to highlight 
> the accessible text (or a portion thereof). Then Orca could call it, 
> Accerciser could call it, low vision tools could call it, reading 
> tools could call it, etc.
>
> Beyond that, toolkits are in a far better position than any other 
> technology to properly highlight that toolkit's own widgets, so you 
> get better highlighting quality. Lastly, this approach would be 
> desktop environment independent.
>
> When this functionality is in place, Orca will use it.

This makes perfect sense. I hadn't thought through the details beyond the
feature itself, but what you suggest is the right footing to start from.

Luke
_______________________________________________
orca-list mailing list
orca-list gnome org
https://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
Log bugs and feature requests at http://bugzilla.gnome.org Find out how to
help at http://live.gnome.org/Orca/HowCanIHelp