Thread Subject: Re: Gaps in Web Requirements-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: Randy Marsden (Home)
Date: Thu, Jan 11 2007 7:05 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Brett, Thomas F: "Re: Gaps in Web Requirements-keyboard operation"
- Messages sorted by: Author | Thread | Date
I agree. A big part of being accessible from the keyboard for people with
mobility impairments has to do with access to the functions in the menus Â
not necessarily the content of the application. This is often done via
on-screen keyboards and scanning arrays that have the keyboard equivalents
for the applicationsÂ¹ functions assigned to a key(s). ThatÂ¹s why one of the
big requests from AT is for IT to provide keyboard equivalents for every
function of an application. In effect, they serve as a type of high-level
As Gregg pointed out, things like Save, clipboard operations, etc., are
accomplished using keyboard equivalents. Not only is the keyboard used to
name the file when it is saved, it can also be used to invoke the save
command in the first place.
> From: "Gregg Vanderheiden" < = EMAIL ADDRESS REMOVED = >
> Reply-To: TEITAC Web/Software Subcommittee
> < = EMAIL ADDRESS REMOVED = >
> Date: Wed, 10 Jan 2007 22:38:38 -0800
> To: "'TEITAC Web/Software Subcommittee'" < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [teitac-websoftware] Gaps in Web Requirements- keyboard operation
> I think that software written to work on a laptop is software that is
> designed for a system that has a keyboard. The software itself may not use
> the keyboard for all functions but the keyboard is part of the system. In
> fact the keyboard is probably used to name the file when it is saved.
> We don't want to say that things need to be accessible from the keyboard
> only if they are designed to be accessible from the keyboard. It should be
> as was suggested - that it is always except when it can't be done for
> technical reasons.
> -- ------------------------------
> Gregg C Vanderheiden Ph.D.
- Next message in Thread: None
- Previous message in Thread: Brett, Thomas F: "Re: Gaps in Web Requirements-keyboard operation"