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 5:10 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Travis Roth: "Re: Group A: 21(a) keyboard operation"
- Previous message in thread: Victor Tsaran: "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
"[victor wrote] If operating system already provides such functionality, I'd
say we should not "have software developers reinvent the same behavior,
rather, in my opinion, we should ask "them to respect operating system's
built-in feature and either let users enable it from "inside the software in
With this line of reasoning software applications shouldn't need to put any
keyboard access in, because mouse keys are available and JAWS has the "JAWS
- Next message in Thread: Travis Roth: "Re: Group A: 21(a) keyboard operation"
- Previous message in Thread: Victor Tsaran: "Re: Group A: 21(a) keyboard operation"