Understanding Documents — Authoritative Guidance for WCAG Criteria

In this tutorial, you will learn about Understanding Documents. We cover key concepts, practical examples, and best practices to help you master this topic.

WCAG Understanding documents provide authoritative guidance for each success criterion including intent, benefits, examples, sufficient techniques, advisory techniques, and failures, serving as the primary reference for implementation and testing.

What You'll Learn

You will learn how to find, read, and use Understanding documents to implement WCAG Compliance correctly.

Why It Matters

The Understanding documents are the authoritative source for interpreting WCAG criteria. Reading only the criterion text often leads to incorrect implementation.

Real-World Use

DodaTech's Accessibility specialists start every new feature by reading the Understanding documents for applicable criteria. This ensures implementation aligns with W3C intent.

flowchart TD
  A[Understanding Document] --> B[Intent]
  A --> C[Benefits]
  A --> D[Examples]
  A --> E[Resources]
  A --> F[Techniques]
  B --> G[Why the criterion exists]
  C --> H[Who benefits and how]
  D --> I[Pass and fail examples]
  F --> J[Sufficient and advisory]
  F --> K[Failures]

What Is in an Understanding Document

Each Understanding document contains: the full criterion text, the intent of the criterion, who benefits from it and how, examples of pass and fail implementations, links to sufficient and advisory techniques, links to failure patterns, and additional resources.

How to Find Understanding Documents

The URL pattern is w3.org/WAI/WCAG22/Understanding/slug.html where the slug uses hyphens instead of dots.

For 1.4.3 Contrast Minimum: w3.org/WAI/WCAG22/Understanding/contrast-minimum.html

For 2.4.11 Focus Appearance: w3.org/WAI/WCAG22/Understanding/focus-appearance.html

How to Read an Understanding Document

Start with the Intent section. Understand why the criterion exists. Read the Benefits section to understand who it helps. Review examples to see correct and incorrect implementations. Follow technique links for implementation guidance.

function getUnderstandingUrl(criterionNumber) {
  const mapping = {
    '1.1.1': 'non-text-content',
    '1.4.3': 'contrast-minimum',
    '2.1.1': 'keyboard',
    '2.4.7': 'focus-visible',
    '2.4.11': 'focus-appearance',
    '3.3.2': 'labels-or-instructions',
    '4.1.2': 'name-role-value'
  };

  const slug = mapping[criterionNumber] || criterionNumber.replace(/\./g, '-');
  return `https://www.w3.org/WAI/WCAG22/Understanding/${slug}.html`;
}

console.log(getUnderstandingUrl('2.4.11'));

Expected output:

https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html

Why Understanding Documents Matter

The success criterion text alone is a single sentence. The Understanding document provides the context needed for correct implementation. Without it, developers often implement solutions that pass a literal reading but fail the intent.

Common Mistakes

1. Never Reading Understanding Documents

Relying only on the criterion text leads to incorrect implementation. Always read the Understanding document.

2. Reading Only the Examples

Examples are helpful but do not cover all scenarios. Read the Intent and Benefits sections for full context.

3. Not Following Technique Links

Understanding documents link to techniques. Following these links provides specific code guidance.

4. Using Outdated Understanding Documents

Each WCAG version has its own Understanding documents. Use the version you are targeting.

5. Ignoring the Resources Section

The Resources section includes research papers, tools, and additional reading that deepen understanding.

6. Not Sharing Understanding Documents with the Team

Understanding documents are team resources. Share links in your documentation and code reviews.

7. Relying on Third-Party Summaries

Third-party summaries may miss important context. Read the original Understanding document.

Practice Questions

1. Where are Understanding documents published?

At w3.org/WAI/WCAG22/Understanding/ with URLs using hyphens instead of dots.

2. What sections does an Understanding document contain?

Intent, benefits, examples, resources, sufficient techniques, advisory techniques, and failures.

3. Why is the Intent section important?

It explains why the criterion exists and what problem it solves. This context is essential for correct implementation.

4. How do Understanding documents help with implementation?

They provide examples, technique links, and failure patterns that guide correct implementation.

5. Challenge: Pick the most relevant WCAG criterion for your current project. Read its Understanding document. Write a one-paragraph summary of the intent and implementation.

FAQ

Mini Project

Create a shortcut list for your team with URLs to the 10 most commonly referenced Understanding documents. Share it in your team's documentation or wiki.

What's Next

Learn about Conformance Claims and how to formally document your WCAG compliance. Then explore Conformance Requirements for complete documentation.