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

Input for F2F on Guide and general techniques

From: David MacDonald <befree@magma.ca>
Date: Thu, 9 Jun 2005 17:36:32 -0400
Message-Id: <200506092136.j59LaaGH012874@mail2.magma.ca>
To: "'John Slatin'" <John_slatin@austin.utexas.edu>, <w3c-wai-gl@w3.org>
Cc: "'Wendy Chisholm'" <wendy@w3.org>, "'Michael Cooper'" <michaelc@watchfire.com>, "'Gregg Vanderheiden'" <gv@trace.wisc.edu>
I would like to provide input for the Face to Face on the General Techniques
document and the Guide to the Guidelines. 

 

There has been talk about whether the General Techniques and the Guide to
the Guidelines should belong in the same document as an "everything you
wanted to know about." document. 

 

I don't mind having one view of the information combined like that but don't
think it should be the core view. I think these two chunks of information
will have very different audiences.  The Guide Doc will appeal to upper
level strategists and policy people who want to more about the reasons *why*
we came up with a certain guideline. The general techniques will appeal to
webmasters and technical people who will want to know *how* to fulfill
general aspects of technical procedures (such as how to write a good alt
text). The techies will come to the general techniques from the technical
documents and the policy people will come to the guide Doc from the GL.
Policy people won't be interested on how to write meaningful alt text and
I'm afraid to say technical people will not care why we made any particular
guideline. They just want to know what to do, and they have a very short
attention span. So I recommend they be developed and shown in separate
documents.

 

Cheers

David MacDonald

 

.Access empowers people
            .barriers disable them.

www.eramp.com

 
Received on Thursday, 9 June 2005 21:36:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC