Re: that darned accessibility capplet

[Bill Haneman <bill haneman sun com>]

On Wed, 2002-10-09 at 19:17, Calum Benson wrote:
> On Wed, 2002-10-09 at 19:08, Bill Haneman wrote:
> 
> > 
> > I still think that calling the MouseKeys tab "mouse" and including a
> > link to the Mouse capplet would be an accessibility improvement.  We
> > certainly can afford the space now, and it's quite relevant to MouseKeys
> > users.
> 
> I'm still faintly unconvinced (probably just because I can't think of a
> realistic scenario where the user would want to use the mouse for some
> things but MouseKeys for others), but I'd certainly be happier with the
> button solution than replicating mouse capplet functionality in what is
> supposed to be a keyboard settings dialog :)

OK, I need to do some experiments then; I am assuming that the Mouse
settings in question (double-click time, Cursors, acceleration,
drag-and-drop threshold) affect the MouseKeys "mouse" as well as the
physical mouse device.  Obviously some of these apply to MouseKeys as
well as the physical mouse, but maybe not all.

For instance, users with mobility issues are likely to want to adjust
drag-and-drop and double-click settings, and low-vision users may prefer
one default cursor over another (probably one of the two "large"
cursors).


-Bill

> Cheeri,
> Calum.
> 
> -- 
> CALUM BENSON, Usability Engineer       Sun Microsystems Ireland
> mailto:calum benson sun com            GNOME Desktop Group
> http://ie.sun.com                      +353 1 819 9771
> 
> Any opinions are personal and not necessarily those of Sun Microsystems
>