Operable — 17 WCAG Criteria
Principle description
The Operable principle ensures that user interface components and navigation must be operable. This includes keyboard accessibility, providing users enough time to read and use content, not designing content in a way that causes seizures, providing navigable ways to find content, and supporting various input modalities beyond keyboard.
The 17 criteria
- 2.1.1A
Keyboard
- 2.1.2A
No Keyboard Trap
- 2.1.4A
Character Key Shortcuts
- 2.2.1A
Timing Adjustable
- 2.2.2A
Pause, Stop, Hide
- 2.3.1A
Three Flashes or Below Threshold
- 2.4.1A
Bypass Blocks
- 2.4.2A
Page Titled
- 2.4.3A
Focus Order
- 2.4.4A
Link Purpose (In Context)
- 2.4.5AA
Multiple Ways
- 2.4.6AA
Headings and Labels
- 2.4.7AA
Focus Visible
- 2.5.1A
Pointer Gestures
- 2.5.2A
Pointer Cancellation
- 2.5.3A
Label in Name
- 2.5.4A
Motion Actuation
Test the “Operable” principle on your site
Scrutia tests all WCAG 2.1 criteria, including the 17 criteria under the Operable principle. Results in 2 minutes.
Audit my site for free