Re: [g-a-devel] Accessibility in Preferred Applications

[Bill Haneman <Bill Haneman Sun COM>]

I agree with Carlos that gnome-mag's 'magnifier' binary should not 
appear in the preferred applications dialog.

However I have some misgivings about separating out "screen reader" and 
"magnifier" in the first place. 

In discussions at the Gnome summit I got the impression that it made 
more sense to just use the existing session-management/startup-program 
facilities to start whatever assistive technologies the end-user wished.

However I think this means keeping the ATs in the main menu somewhere - 
if not in the main 'Applications' menu, at least in an "Assistive 
Technologies" or "Universal Access" submenu of Applications.  I have 
misgivings about moving them into the 'Accessibility' or 'AT' dialog, as 
Henrik proposes, and have come to doubt the appropriateness of putting 
them in the "Preferred Applications" menu.

Possibly the right approach is to modify the GUI for the "Assistive 
Technology Support" dialog so that the 
"screenreader"/"magnifier"/"onscreen keyboard" checkboxes go away, and 
are replaced by a facility for choosing one or more applications from 
the "AT" category.  I think such categorization of apps can be done via 
the apps' ".desktop" files, so such a dialog could find all applications 
that self-identified as assistive technologies and present them in such 
a GUI.

Bill

Carlos Eduardo Rodrigues Diógenes wrote:
> On Fri, 2006-12-01 at 12:54 -0600, George Kraft IV wrote:
>   
> > On Fri, 2006-12-01 at 13:49 -0200, Carlos Eduardo Rodrigues Diógenes
> > wrote:
> >     
> > > I don't think that the *Magnifier* option must be removed. I only
> > > think
> > > that gnome-mag can't be presented in it, since it is not a stand alone
> > > magnifier like kmag or others!
> > >       
> > I had the impression that standalone "magnifier -m" provides mouse
> > tracking which is not to be confused with focus and caret tracking done
> > by a screen reader.  Different combinations of ATs and accessible
> > applications provide different levels of detail.  One should not assume
> > standalone "magnifier -m" is broken, but rather a the user is
> > requestiong a different level detail.
> >     
>
> But it is not confortable yet IMO, since I can't close the gnome-mag
> applications when it's running stand-alone, I also can't choose size,
> position, mag factor while the application is running. If I was an user
> from an application that can just be started and then finished with a
> *kill* I will not feel confortable.
>
>   
> > Under *Magnifier*, we could label it "Standalone GNOME Magnifier", and
> > under *Screen Reader* label it "Gnopernicus with Magnification".  The
> > end-user would select either one or the other.
> >     
>
> Maybe the gnome-mag option in *Magnifier* stay disabled and the other
> enabled for selection and when the user set the *Screen Reader* option
> *Run at start* the gnome-mag option in *Magnifier* become available (if
> the *Screen Reader* selected really use gnome-mag).
>
> Maybe when the *GNOME Magnifier* option is disabled it could appear as
> *GNOME Magnifier (Screen Reader dependent)*.
>
> What do you think about?
>
>   
> > I very much appreciating your help in this use case scenario.
> >
> > Best regards,
> >
> > George (gk4)
> >
> >
> >