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

Re: Guideline 2.1 proposals

From: Charles McCathieNevile <charles@w3.org>
Date: Wed, 2 Jun 1999 15:34:07 -0400 (EDT)
To: Bruce_Roberts/CAM/Lotus@lotus.com
cc: w3c-wai-au@w3.org
Message-ID: <Pine.LNX.4.10.9906021518280.2065-100000@tux.w3.org>
TRACE, ATRC, IBM, American Foundation for the Blind, are all members of the
group, and publish extensively in the field. My review of the area over the
last two weeks suggests that IBM, Microsoft, EITAAC, and Sun have all relied
extensively on the work of TRACE. (As an historian, an important part of my
expertise is looking at documents and determining what the dependencies are.
It was an interesting exercise in this case.) Although I doubt that any one
member of the group has sufficient expertise to create this information from
nothing, I think the required expertise and the necessary background
information are in fact readily available within working group. Part of that
expertise is an understanding of what information a developer needs, and how
best to present it. Your (Bruce's) expertise in that particular area is an
important ingredient.

I haven't come up with this information because I am some kind of genius. The
checkpoints as I have proposed are those which seem, after discussion and
reflection, to provide the necessary information for what must be done. The
techniques I have collected and proposed are based on careful review of the
following documents:

    "Macintosh Human Interface Guidelines" available at:


    "Requirements for Accessible Software Design" US Department of Education,
    version 1.1 March 6, 1997. Available at:


    "EITACC Desktop Software standards" Electronic Information Technology
    Access Advisory (EITACC) Committee. Available at:


    "Software Accessibility" IBM Special Needs Systems. Available at:


    "MS checklist" available at:


    "Designing for Accessibility" Eric Bergman and Earl Johnson. Available at:


    "Towards Accessible Human-Computer Interaction" Eric Bergman, Earl
    Johnson, Sun Microsytems 1995. A substantial paper, with a valuable print
    bibliography. Available at:


    "Accessibility quick reference guide" Sun Microsystems. Not as useful as
    [SUN-DESIGN][8]. Available at:


    "Application Software Design Guidelines" compiled by G. Vanderheiden. A
    thorough reference work. Available at:


    "User Agent Accessibility Guidelines (Working Draft)" J. Gunderson, I.
    Jacobs eds. This is a work in progress, and the latest working draft is
    available at:


    "Web Content Accessibility Guidelines 1.0" W. Chisholm, I. Jacobs, C.
    LeTourneau, G. Vanderheiden eds. Guidelines for accessible web content,
    available at:


    "What is Accessible Software" James W. Thatcher, Ph.D., IBM, 1997. This
    paper gives a short example-based introduction to the difference between
    software which is accessible, and software which can be used by some
    assitive technologies. Available at


Charles McCN

On Wed, 2 Jun 1999 Bruce_Roberts/CAM/Lotus@lotus.com wrote:

       I'm still uncomfortable with having multiple tool accessibility
  checkpoints.  I'm O.K. (marginally) with the checkpoint for following the
  operating system standards with a large list of techniques behind it.  Beyond
  that, I would like to be convinced that this group has the correct expertise and
  can spend the appropriate time to define other UI accessiblity requirements.  I
  know I don't have that expertise or the time.  Can other folks speak to this?
  -- Bruce
Received on Wednesday, 2 June 1999 15:34:41 UTC

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