WCAG 2.1 Success Criteria Overview
You'll learn: How WCAG organizes accessibility requirements into testable, measurable success criteria that guide developers toward compliant implementations.
What Are Success Criteria?
Think of WCAG success criteria like building code inspections for accessibility. Just as a building inspector checks specific requirements (exit width, railing height, etc.), success criteria provide specific, testable checkpoints to verify if your website meets accessibility standards.
Each success criterion is a statement that's either true or false for your content—there's no gray area. This makes accessibility measurable rather than subjective.
The Structure
Success criteria are organized under the four POUR principles you already know (Perceivable, Operable, Understandable, Robust). Each criterion includes:
- A unique number (like 1.1.1 or 2.4.7)
- A descriptive name (like "Non-text Content" or "Focus Visible")
- A conformance level (A, AA, or AAA)
- Testable requirements written clearly
For example, Success Criterion 2.1.1 "Keyboard" (Level A) states: "All functionality of the content is operable through a keyboard interface." You can test this—try navigating your site without a mouse. If you can't reach something, you fail this criterion.
Why This Matters
Success criteria transform vague goals like "make it accessible" into concrete actions: "Ensure all form inputs have associated labels" (4.1.2) or "Provide text alternatives for images" (1.1.1). This specificity helps you know exactly what to build and how to test it.
Key Takeaway: WCAG success criteria break accessibility down into specific, testable requirements organized by principle and conformance level, giving developers clear targets to meet rather than ambiguous guidelines.