Part of Item:
Comment Type: GE
Comment (including rationale for proposed change):
This reference document is highly accessible in
my hardware and software environment, and the
material is well organized, offering a
summary of each technique with a link to the full
explanation in the techniques documents.
I am confident this reference will be useful to
content developers who want to know how to apply
the guidelines with their chosen technologies,
wish to avoid working through lengthy techniques
documents, but find the application of the
high-level success criteria in the normative
document not to be straightforwardly obvious.
Consider whether to add a view in which all the
glossary definitions in the guidelines are
(optionally, of course) inserted into the body of
the document, as in the \"key terms\" sections of
\"Understanding WCAG 2.0\".
Consider also whether to publish the PHP source
code of the quick reference in case developers
want to install it on their intranets.
I would further suggest that when WCAG 2.0
reaches the Candidate Recommendation stage, a
prominent link be provided from the normative
guidelines document to the Quick Reference. For
many developers, I expect, the Quick Reference
will be the preferred means of reading the
All of the definitions are linked to directly from the words in the Quick Reference. Clicking on any term will take you to the relevant item in the glossary. The glossary itself is quite long, so we do not want to include it directly in the Quick Reference.
We have added links from the Guidelines to the Quick Reference. The How To Meet links for the success criteria now take the reader to the Quick Reference instead of the Understanding document.
With regard to the source code - we will be consider this in conjunction with the EO working group as the Quick Reference becomes stable.