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

Overview WCAG 2.0 edits & questions

From: Shawn Henry <shawn@w3.org>
Date: Tue, 02 May 2006 22:00:55 -0500
Message-ID: <44581CE7.5000307@w3.org>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>, Judy Brewer <jbrewer@w3.org>, Gregg Vanderheiden <po@trace.wisc.edu>, John M Slatin <john_slatin@austin.utexas.edu>, Wendy A Chisholm <wendy@w3.org>, Ben Caldwell <caldwell@trace.wisc.edu>

EOWG Participants & WCAG Editors,

I made most of the changes from Friday's EOWG teleconference to "Overview of WCAG 2.0 Documents" at:
(The previous version is available at: http://www.w3.org/WAI/intro/wcag20-old )
Changes are listed in the changelog at: 

Please comment on the proposed additions below. I hope to put these in place yet this week.

Change requests pending:
* make it clear that Understanding is the document to read
* consider identifying the audience for the different documents, to help clarify who should read them and how they are designed

Proposed additions:

1. under <h2>"WCAG 2.0 Working Draft Documents", in <h3>"Understanding WCAG 2.0" section, at the end (after the list), add a paragraph:
"Understanding WCAG 2.0 will be the primary document that many people use to learn and apply WCAG 2.0, as it lists each guideline and success criteria from WCAG 2.0 along with the additional information described above."

[Ed note: I strongly suggest adding something like this] 

Note that I already edited the first paragraph to be: "Understanding WCAG 2.0 is a guide to learning and implementing WCAG 2.0. It provides extensive guidance to help understand the intent of each guideline and success criteria, and it lists techniques to meet each success criteria." And after that is the list of sections for each success criteria. Comments welcome.

2. under <h2>"WCAG 2.0 Working Draft Documents", in <h3>"WCAG 2.0" section, at the end, add a paragraph:
"WCAG 2.0 will replace WCAG 1.0, and be the formal, stable document for references, such as in policies."
OR the less scary, more vague:
"WCAG 2.0 will be the stable document for formal references."

[Ed note: I mildly suggest adding something like this, but am fine leaving it off if it seems too problematic]

3. none other
- I don't think we need to add anything about audience to Techniques (or Application Notes) - I hope what we have there now makes it clear enough that it's primarily for developers.
- I don;t think we want to add anything about audience for About Baselines doc, because most everyone will need to at least skim the doc, and certain level policy makers, Web project managers, and some others will need to study it in detail. It would be difficult to define and communicate that succinctly.

Thanks for any quick replies.

Received on Wednesday, 3 May 2006 03:01:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:54 UTC