- From: Gregory J. Rosmaita <unagi69@concentric.net>
- Date: Wed, 06 Oct 1999 15:59:35 -0400
- To: pjenkins@us.ibm.com
- Cc: Authoring Tools Guidelines List <w3c-wai-au@w3.org>, Janina Sajka <janina@afb.net>
aloha, again, phil!
phil wrote:
>Why don't we also include KEYBOARD ACCESS, which in my opinion is even
>more important that accessible help? If you don't have keyboard access
>you may not even be able to use the product.
if 7.1 does include all things sub and supralunar, then doesn't it also demand
that in order to satisfy 7.1, one must offer full keyboard access -- for the
help system, as well as for the manipulation of the tool itself? keyboard
access (unlike documentation) is mentioned specifically in the Techniques for
7.1 under the header "Input Device Independence" -- and is specifically
addressed in our sister document, the User Agent Guidelines (guideline 2:
"Ensure keyboard access to user agent functionalities") -- as well as in the
referenced guidelines issued by Trace, IBM, and Microsoft -- all of which
outline the principles of accessible software design -- not to mention the
standards documents, such as those promulgated by EiTAAC, which are also
referenced in the AU Techniques document...
gregory
--------------------------------------------------------
He that lives on Hope, dies farting
-- Benjamin Franklin, Poor Richard's Almanack, 1763
--------------------------------------------------------
Gregory J. Rosmaita <unagi69@concentric.net>
WebMaster and Minister of Propaganda, VICUG NYC
<http://www.hicom.net/~oedipus/vicug/index.html>
--------------------------------------------------------
Received on Wednesday, 6 October 1999 15:54:01 UTC