Each WCAG success criterion has a specific structure that can seem opaque at first. Reading them precisely is essential because accessibility audits, legal agreements, and conformance claims are all based on the exact wording. Here is how to parse any WCAG criterion.
Number and short name
Each criterion has a numeric identifier with three parts: principle.guideline.criterion. For example, 1.4.3 means Principle 1 (Perceivable), Guideline 4 (Distinguishable), Criterion 3 (Contrast Minimum). The short name is the human-readable title, e.g., "Contrast (Minimum)". Automated scanners and reports typically reference criteria by both number and short name.
Normative text and intent
The normative text is the actual criterion — the precise statement you must satisfy. The intent is non-normative explanatory material that helps you understand what the criterion aims to achieve. When there is ambiguity, the normative text governs.
Understanding documents and techniques
The W3C publishes "Understanding WCAG" documents for each criterion that include the intent, benefits, examples, related resources, and a list of techniques. Techniques are either "sufficient" (they definitely satisfy the criterion), "advisory" (they go beyond the criterion), or "failures" (they are known to violate the criterion). Techniques are informative — they are not the only ways to meet a criterion.
Note
Automated scanners can only detect a fraction of WCAG violations — typically around 30-40% of testable criteria. The rest require manual testing, particularly criteria under Understandable and some Operable criteria.
Exceptions and applicability
Most criteria include a scope statement or note explaining when they apply. For example, 1.4.3 has exceptions for decorative text, logos, and inactive UI components. Reading the full criterion — not just the headline — prevents both over-reporting violations and missing genuine failures.