Skip to main content

Back to Guidelines

What is Motion Actuation?

Functions triggered by motion have an alternative control and can be disabled.

Functions triggered by motion have an alternative control and can be disabled.

Keyboard and screen reader users.
People who need predictable interactions.
Users who benefit from visible focus and clear labels.

Good vs Bad Examples

Use the tabs to compare the accessible pattern with the example to avoid.

Good Example 1 – Undo Button + Optional Shake Gesture

Notes app showing an Undo button with an optional shake-to-undo setting that can be disabled.

html

<button type="button">Undo</button>
<label><input type="checkbox" /> Enable Shake to Undo (optional)</label>

Why this is correct (developer logic):

Undo feature is available through a button.
Motion gesture is optional.
Users can disable motion activation.

Good Example 2 – Accessible Banking Confirmation

Banking transfer screen showing Confirm Transfer and Cancel buttons with an optional tilt-to-confirm setting.

html

<button type="button">Confirm Transfer</button>
<label><input type="checkbox" /> Enable Tilt to Confirm (optional)</label>

Why this is correct (developer logic):

Primary action is available through standard controls.
Motion interaction is optional.
Accessible for all users regardless of device movement.

Implementation Checklist

Progress0 / 5 completed (0%)

Keep the interaction predictable and easy to understand.
Test with keyboard and screen reader navigation.
Make sure focus is visible and easy to track.
Avoid hidden, unexpected, or unnecessary repetition.
Confirm the example meets the intended accessibility requirement.

Knowledge Check

Answer Yes or No to test your understanding of motion actuation.

Score: 0 / 3 · Answered: 0 / 3

Does the good example demonstrate motion actuation correctly?

Is the bad example acceptable for motion actuation?

Should this pattern be checked with keyboard and screen reader testing?