In this project, we are redesigning what WCAG supporting documents look like, with the goals of making them easier to discover, navigate and apply to web projects (full requirements analysis).
Prototypes and templates
Work in progress templates
Page “All WCAG 2.1 guidance”
The supporting documents are “stand-alone” from the WAI website: they don't contain the full WAI header and navigation. To bridge between these documents and the WAI website and provide context, we will link to the WCAG documents page on the WAI website.
This is where users of one document (e.g. a specific Technique) can find out which other documents exists (Techniques, Understanding, COGA Guidance, etc).
User: I want to find out which set this document is part of
Blue header at the top has name of the set of documents, for instance “WCAG 2.1 Techniques”.
User: I want to know what kind of document I am looking at
Sidebar contains short sentence that explains the kind of document, for instance “Techniques are examples of ways to meet a WCAG success criterion.”, and there is a link to “About Techniques” in the top navigation.
User: I want to know if the document is “required” (normative or informative)
This should be clear from the sidebar sentence, can be further explained in the “About” page linked from the header.
User: I want to know if guidance is accurate / recent
@@TODO@@ Banner to be displayed if guidance is outdated