Loading Developer Playground

Loading ...

Skip to main content
Developer Playground
Share:
Back to WCAG Explorer

Success Criterion · WCAG 2.5.4

Motion Actuation

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when supported motion is essential or not using motions would invalidate the activity.

Level AWCAG 2.1Operable2.5 · Input Modalities
Copy button ready

Success criterion

What WCAG 2.5.4 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

All non-text content that is presented to users must expose an equivalent text-based alternative unless a documented exception applies.

View Understanding 2.5.4Open QuickRef techniques

Fast facts

Conformance level
Level A
WCAG version introduced
WCAG 2.1
Principle
Operable
Guideline
2.5 · Input Modalities

Implementation checklist

Capture progress and blockers

  • Document how this criterion impacts your product and note any exceptions.
  • Describe the user experience goal in plain language for designers and engineers.
  • List the components, templates, or workflows that must meet this requirement.
  • Capture manual and automated testing steps for future audits.

Testing ideas

Prove conformance with evidence

  • Pair automated linting with human review to verify visual, auditory, or temporal aspects.
  • Use assistive technology walkthroughs (screen reader, keyboard, switch, voice) to validate behavior.
  • Capture screenshots or recordings that demonstrate pass/fail conditions.

Related success criteria

More from Input Modalities (2.5)

View all criteria
WCAG 2.5.1Pointer GesturesLevel AWCAG 2.5.2Pointer CancellationLevel AWCAG 2.5.3Label in NameLevel AWCAG 2.5.5Target Size (Enhanced)Level AAAWCAG 2.5.6Concurrent Input MechanismsLevel AAAWCAG 2.5.7Dragging MovementsLevel AAWCAG 2.5.8Target Size (Minimum)Level AA
Back to WCAG Explorer