WCAG 2.1 Operable: Every Success Criterion Explained

This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.

WCAG 2.1 guidelines hub → Operable

The Operable principle is the second of WCAG 2.1’s four principles: user interface components and navigation must be operable — meaning every interaction has to work for someone who can’t use a mouse, has limited time or motor precision, or is sensitive to flashing or motion. In practice, this is the principle that governs keyboard access, focus management, time limits, seizure-inducing content, navigation aids, and touch/pointer input. It has five guidelines and 29 success criteria, from Level A (the baseline) through AA (Quietramp’s audit standard) to AAA (the strictest tier, rarely mandated but useful to know).

This page covers every Operable success criterion in WCAG 2.1, in order — each one now has its own dedicated page linked below. Numbers, names, and levels are drawn from the official WCAG 2.1 quick reference, which is the source to check for current normative wording. See also our companion page on the Perceivable principle.

Contents

Every success criterion below now has its own dedicated page — the list here is grouped by guideline for quick scanning.

2.1 Keyboard Accessible

• 2.1.1 Keyboard (Level A)
• 2.1.2 No Keyboard Trap (Level A)
• 2.1.3 Keyboard (No Exception) (Level AAA)
• 2.1.4 Character Key Shortcuts (Level A)

2.2 Enough Time

• 2.2.1 Timing Adjustable (Level A)
• 2.2.2 Pause, Stop, Hide (Level A)
• 2.2.3 No Timing (Level AAA)
• 2.2.4 Interruptions (Level AAA)
• 2.2.5 Re-authenticating (Level AAA)
• 2.2.6 Timeouts (Level AAA)

2.3 Seizures and Physical Reactions

• 2.3.1 Three Flashes or Below Threshold (Level A)
• 2.3.2 Three Flashes (Level AAA)
• 2.3.3 Animation from Interactions (Level AAA)

2.4 Navigable

• 2.4.1 Bypass Blocks (Level A)
• 2.4.2 Page Titled (Level A)
• 2.4.3 Focus Order (Level A)
• 2.4.4 Link Purpose (In Context) (Level A)
• 2.4.5 Multiple Ways (Level AA)
• 2.4.6 Headings and Labels (Level AA)
• 2.4.7 Focus Visible (Level AA)
• 2.4.8 Location (Level AAA)
• 2.4.9 Link Purpose (Link Only) (Level AAA)
• 2.4.10 Section Headings (Level AAA)

2.5 Input Modalities

• 2.5.1 Pointer Gestures (Level A)
• 2.5.2 Pointer Cancellation (Level A)
• 2.5.3 Label in Name (Level A)
• 2.5.4 Motion Actuation (Level A)
• 2.5.5 Target Size (Level AAA)
• 2.5.6 Concurrent Input Mechanisms (Level AAA)

---

This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.

This page was drafted with AI assistance and reviewed by a person for accuracy before publication.

↑ Back to the WCAG 2.1 guidelines hub · See also WCAG 2.1 Perceivable: Every Success Criterion Explained, continue to WCAG 2.1 Understandable: Every Success Criterion Explained, or see how a real audit catches what automated scanning misses in a sample report.