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

Document Links Example

From: Alan Chuter <achuter@teleservicios.com>
Date: Fri, 30 Jul 2004 11:02:36 +0200
To: "EOWG" <w3c-wai-eo@w3.org>
Message-ID: <WorldClient-F200407301102.AA02360106@teleservicios.com>

Perhaps an explanaion of the reason for the document would be useful at
the beginning, for example: "WCAG consists of a series of inter-related
documents. While this structure reduces redundancy and enables the reader
to focus on one aspect [or some other rationale] it can be confusing to
non-experts. This page attempts to explain the relationships between the
documents and assist in navigating among them."

WCAG doesn't actually mention the "Techniques Gateway", rather the links
are just "Techniques for checkpoint X". Maybe this needs explaining.

Perhaps the priority explanation ("Each checkpoint is assigned a
priority...") can be removed to keep the document shorter.

The checklist is perhaps easy to understand, and doesn't need explaining
here. This page is very long-winded; I wonder whether people will have the
patience to read something so long and complicated. I feel that the text
examples dominate the page and make it overwhelming and obscure the
pathway that it tries to illustrate.

I wonder whether this could be explained more clearly by a real-world
scenario. For example the designer has something that doesn't comply with
a checkpoint and follow the path through the documents to reach specific
technique.

regards,

Alan Chuter
achuter@teleservicios.com
Received on Friday, 30 July 2004 05:04:06 UTC

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