W3C home > Mailing lists > Public > w3c-wai-au@w3.org > October to December 1999

RE: proposed addition to intro for GL7

From: Gregory J. Rosmaita <unagi69@concentric.net>
Date: Tue, 19 Oct 1999 01:14:30 -0400
Message-Id: <4.1.19991019010538.00a82ba0@pop3.concentric.net>
To: Charles McCathieNevile <charles@w3.org>
Cc: Authoring Tools Guidelines List <w3c-wai-au@w3.org>, janina@afb.net
aloha, charles!

Guideline 12 of the 5 October draft of the User Agent Guidelines [1] reads:

Provide accessible product documentation and help

Ensure that the user can learn about software features, notably those that
relate to accessibility.

Some people cannot use printed documentation. Vendors should provide accessible
electronic documentation for users with visual impairments, learning
disabilities, or movement impairments. Providing alternative hardcopy formats
may also benefit some users. 

Since users who are not disabled are generally unaware of software features
designed specifically for accessibility, those features should be clearly
documented. This will allow users with disabilities to learn about the software
more easily. 

Documentation includes all product documentation, notably installation
instructions, the help system, and all product manuals. Refer also to guideline
2 and checkpoint 6.6.

if it is the last paragraph to which you are referring, then i'm all for it...
if you also want to quote the introduction to UAAG GL12 verbatim in the ATAG
techniques, i'll sign up for that, too...


[1] http://www.w3.org/WAI/UA/WAI-USERAGENT-19991005/#gl-accessible-doc

At 12:56 AM 10/19/99 Charles McN wrote:
>We should take the same approach as User Agent and say "an accessible version
>of dcumentation must be available", or some such. (I think htey use better
>language, but it is late - I'll look into it tomorrow.
>On Mon, 18 Oct 1999, Gregory J. Rosmaita wrote:
>  At 05:13 PM 10/18/99 Dick Brown wrote:
>  >Gregory, does your inclusion of "the documentation distributed with the
>  >tool" imply that printed documentation has to be accessible?
>  aloha, dick!
>  mea culpa -- i should have typed "electronic documentation" -- believe you 
>  i don't expect anyone other than the vendor of a targetted user agent or an
>  assistive technology to ship braille documentation by default!
>  it does, however, need to be made clear in the techniques for ATAG that the
>  term "electronic documentation" covers not only what is burned onto the
>  distribution CD, but any documentation and/or support mechanisms that are
>  mounted on the web -- they must be WCAG conformant...
>  so should any auto-update or auto-installation process -- such as "connect
>  web", online update wizards, and the like...  
>  checkpoint 7.1, after all, it has been noted on this list in the past,
>  the accessibility of the installation process as well as the tool as a
>  whole...  hmm...  we do have techniques that address the installation 
>  don't we, or have i just issued myself a new action item?
>  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>
>  --------------------------------------------------------
>--Charles McCathieNevile            mailto:charles@w3.org
>phone: +1 617 258 0992   http://www.w3.org/People/Charles
>W3C Web Accessibility Initiative    http://www.w3.org/WAI
>MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA

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
Received on Tuesday, 19 October 1999 01:08:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:43 UTC