W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > July to September 2004

WCAG 2.0 jungle

From: <michaeka@wellsfargo.com>
Date: Thu, 26 Aug 2004 15:34:22 -0700
Message-ID: <4FE9AD0A3D28CE42A163544072FE86760605EC2E@msgsw55cacah01.wellsfargo.com>
To: w3c-wai-eo@w3.org

Hello, all -

Regarding WCAG 2.0 et al., I think there are too many documents, which makes
navigation confusing. 

Rather than have the three layers described in WCAG 2.0 "How to read this
document" (http://www.w3.org/TR/WCAG20/#how-to), layers two and three could
be combined into one. The checklist and application info for each technology
would be combined into one technology document (or "document site" if it was
decided to split the document into separate Web pages). 

This way, the user is either at the overall WCAG 2.0 document or at the
document for a specific technology, which would make it easier for users to
know where they are. 

The Gateway to Techniques for WCAG 2.0
(http://www.w3.org/TR/2004/WD-WCAG20-GATEWAY-20040730/) adds yet another
document to the mix. I also find it confusing, both in content and design.
Its content could be moved to WCAG 2.0 or to the specific technology
documents (or "technology document sites").

Each guideline in WCAG 2.0 could include information on:
a. Explanation of what the guideline is - for example:
http://www.w3.org/TR/2004/WD-WCAG20-GATEWAY-20040730/guideline1.1.html.
Maybe this could be a simple description with a link to a more in-depth
description of the guideline.
b. Success criteria of the guideline - for example,
http://www.w3.org/TR/WCAG20/#text-equiv
<http://www.w3.org/TR/WCAG20/#perceivable
c. Link to Who Benefits
d. Link to Examples
e. Links to specific technology guidelines

Regards,

Blossom
_____________________________________
Blossom Michaeloff
Web Research and Design
Wells Fargo
415.222.3045
michaeka@wellsfargo.com
Received on Thursday, 26 August 2004 22:34:56 UTC

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