Thread Subject: Re: Group A: 21(a) keyboard operation
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Luke Kowalski
Date: Thu, Oct 19 2006 11:45 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jonathan Avila: "Re: Group A: 21(a) keyboard operation"
- Previous message in thread: Jonathan Avila: "Re: Group A: 21(a) keyboard operation"
- Messages sorted by: Author | Thread | Date
[Peter korn wrote] Today all three desktop OSes (Windows, Mac, and UNIX) provide MouseKeys functionality that allows any user who can press a single key on the keypad to move the mouse. Is this reasonable and sufficient? Or should we actually require that every software application provide mouse movement alternatives for moving things like spray cans in painting programs?
I would like to second Peter's comment about deferring this to the OS layer. Overriding standard mouse control at the OS level with different/local app settings would prob be in conflict with ISO and WCAG points about not breaking interop. Besides...Consistency issues would surface shortly if this were up to each individual authoring app. If there are issues with mousekyes not working in a particular Linux, Windows, or Mac OS, it is probably a separate thing to consider.
The point made earlier about the shapes drawn not being discernible by the reader is also something to mull over as a factor.
luke kowalski, CPE
Corporate UI Architect
Redwood Shores, CA 94065
650 506 1227
- Next message in Thread: Jonathan Avila: "Re: Group A: 21(a) keyboard operation"
- Previous message in Thread: Jonathan Avila: "Re: Group A: 21(a) keyboard operation"