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: Jonathan Avila
Date: Thu, Oct 19 2006 12:35 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Barrett, Don: "Re: Group A: 21(a) keyboard operation"
- Previous message in thread: Luke Kowalski: "Re: Group A: 21(a) keyboard operation"
- Messages sorted by: Author | Thread | Date
//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. //
I wasn't in any way suggesting that software move the mouse pointer or
provide keys to move the mouse pointer. I was instead suggesting that all
mouse operations be supplemented by keyboard actions. Others have agreed
that having MouseKeys in the OS shouldn't be an OS requirement. If it is
not an OS requirement and not a software requirement then a user will then
need to bring an AT into the mix.
- Next message in Thread: Barrett, Don: "Re: Group A: 21(a) keyboard operation"
- Previous message in Thread: Luke Kowalski: "Re: Group A: 21(a) keyboard operation"