Overview of WCAG

I have been away on vacation for the past few weeks, so I've missed the
discussion of these pages, which is why these comments are arriving so late.

I think that the structure of WCAG and the techniques document is rather
complex. There is a hierarchy from bstract to concrete, that might be
better illustrated as a diagram. Here's my suggestion:
http://www.infoescena.es/achuter/wai/wcag_struct.svg
http://www.infoescena.es/achuter/wai/wcag_struct.png

We don't mention Section 508, which confuses people. Perhaps we should
explain the differences.

I think it needs to explain more clearly the progression from abstract
guidlines to specific techniques. The second sentence "Each guideline has
one or more checkpoints that explain how the guideline applies in a
specific area." Could say something like "Each general guideline has one
or more specific checkpoints that explain how the guideline applies in a
specific area."

The sentence "Each checkpoint is assigned a priority and has a link to
Techniques." has two different ideas in one phrase. Maybe they should be
separated. It should explain that there is a Techniques document before
switching ideas in mid-sentence. For example, "A series of techniques
documents give practical suggestions about how to comply with the
checkpoints. Each checkpoint is linked to the different techniques documents."

I think perhsps the CSS and HTML techniques links are self-explanatory and
don't need the accompanying text. The Core techs does.

Sidebar: The link to the ordering quick tips page would be confusing if
you don't understand that there is a print version. Maybe this could be
removed. The translation link might be better in the main section, with an
explanation "Translations available".

regards,

Alan Chuter
achuter@teleservicios.com

Received on Friday, 30 July 2004 04:33:20 UTC