WCAG 2.1 success criteria
All 78 WCAG 2.1 success criteria with plain-language summaries, common failure modes, and fix techniques. Maintained by the mandatiq accessibility team.
Perceivable
Information and UI components must be presentable in ways users can perceive — text alternatives, captions, contrast, adaptable layouts.
- 1.1.1ANon-text Content
- 1.2.1AAudio-only and Video-only (Prerecorded)
- 1.2.2ACaptions (Prerecorded)
- 1.2.3AAudio Description or Media Alternative (Prerecorded)
- 1.2.4AACaptions (Live)
- 1.2.5AAAudio Description (Prerecorded)
- 1.2.6AAASign Language (Prerecorded)
- 1.2.7AAAExtended Audio Description (Prerecorded)
- 1.2.8AAAMedia Alternative (Prerecorded)
- 1.2.9AAAAudio-only (Live)
- 1.3.1AInfo and Relationships
- 1.3.2AMeaningful Sequence
- 1.3.3ASensory Characteristics
- 1.3.4AAOrientation
- 1.3.5AAIdentify Input Purpose
- 1.3.6AAAIdentify Purpose
- 1.4.1AUse of Color
- 1.4.2AAudio Control
- 1.4.3AAContrast (Minimum)
- 1.4.4AAResize Text
- 1.4.5AAImages of Text
- 1.4.6AAAContrast (Enhanced)
- 1.4.7AAALow or No Background Audio
- 1.4.8AAAVisual Presentation
- 1.4.9AAAImages of Text (No Exception)
- 1.4.10AAReflow
- 1.4.11AANon-text Contrast
- 1.4.12AAText Spacing
- 1.4.13AAContent on Hover or Focus
Operable
All UI components and navigation must be operable — keyboard support, enough time, no seizure-inducing motion, navigability, and input modalities.
- 2.1.1AKeyboard
- 2.1.2ANo Keyboard Trap
- 2.1.3AAAKeyboard (No Exception)
- 2.1.4ACharacter Key Shortcuts
- 2.2.1ATiming Adjustable
- 2.2.2APause, Stop, Hide
- 2.2.3AAANo Timing
- 2.2.4AAAInterruptions
- 2.2.5AAARe-authenticating
- 2.2.6AAATimeouts
- 2.3.1AThree Flashes or Below Threshold
- 2.3.2AAAThree Flashes
- 2.3.3AAAAnimation from Interactions
- 2.4.1ABypass Blocks
- 2.4.2APage Titled
- 2.4.3AFocus Order
- 2.4.4ALink Purpose (In Context)
- 2.4.5AAMultiple Ways
- 2.4.6AAHeadings and Labels
- 2.4.7AAFocus Visible
- 2.4.8AAALocation
- 2.4.9AAALink Purpose (Link Only)
- 2.4.10AAASection Headings
- 2.5.1APointer Gestures
- 2.5.2APointer Cancellation
- 2.5.3ALabel in Name
- 2.5.4AMotion Actuation
- 2.5.5AAATarget Size
- 2.5.6AAAConcurrent Input Mechanisms
Understandable
Information and UI operation must be understandable — readable text, predictable behaviour, helpful input assistance.
- 3.1.1ALanguage of Page
- 3.1.2AALanguage of Parts
- 3.1.3AAAUnusual Words
- 3.1.4AAAAbbreviations
- 3.1.5AAAReading Level
- 3.1.6AAAPronunciation
- 3.2.1AOn Focus
- 3.2.2AOn Input
- 3.2.3AAConsistent Navigation
- 3.2.4AAConsistent Identification
- 3.2.5AAAChange on Request
- 3.3.1AError Identification
- 3.3.2ALabels or Instructions
- 3.3.3AAError Suggestion
- 3.3.4AAError Prevention (Legal, Financial, Data)
- 3.3.5AAAHelp
- 3.3.6AAAError Prevention (All)
Robust
Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.
- 4.1.1AParsing
- 4.1.2AName, Role, Value
- 4.1.3AAStatus Messages