Goal
Prevent accidental activation from pointer down events.
Success Criterion · WCAG 2.5.2
Pointer Cancellation
For functionality that can be operated using a single pointer, at least one of the following is true: no down-event is used to execute the function, the completion of the function is on the up-event and a mechanism is available to abort or undo the function, the up-event reverses any outcome of the preceding down-event, or completing the function on the down-event is essential.
Level AWCAG 2.1Operable2.5 · Input Modalities
Copy button ready
What to do
Ensure actions happen on pointer up, can be canceled, or have an undo/confirm option.
Why it matters
Users with tremors or motor impairments may accidentally activate controls if they trigger on touch down.
Success criterion
What WCAG 2.5.2 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
For functionality that can be operated using a single pointer, at least one of the following is true: (1) No Down-Event: The down-event of the pointer is not used to execute any part of the function; (2) Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; (3) Up Reversal: The up-event reverses any outcome of the preceding down-event; (4) Essential: Completing the function on the down-event is essential.
Intent
Why WCAG created this requirement
- Pointer down triggers are easy to activate accidentally.
- Users should be able to cancel or undo actions.
- This applies to mouse, touch, stylus, and similar pointer inputs.
Benefits
Who gains when you pass
- Users with tremors can avoid accidental activation.
- Touch users can slide finger away to cancel before releasing.
- All users benefit from fewer unintended clicks and safer interactions.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Accidental pointer down activation can cause destructive actions (delete, purchase).
Users may lose data or trigger navigation unexpectedly.
Exception guidelines
Use the WCAG 2.5.2 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Essential
Down-event activation is essential to the function.
Requirement
Use only when essential (rare).
Overview
Avoid firing actions on pointer down. Prefer pointer up (click release) and allow cancellation, undo, or reversal when needed. This reduces accidental activations.
- Trigger primary actions on `click`/pointer up, not on `mousedown`/`pointerdown`.
- Provide undo for destructive actions where possible.
- Long-press interactions should have clear cancellation behavior.
Reference: All summaries and highlights originate from Understanding WCAG 2.5.2 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.1
- Principle
- Operable
- Guideline
- 2.5 · Input Modalities
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Delete button
Pass
Delete triggers on click release and offers undo or confirmation.
Fail
Delete triggers immediately on mousedown/touchstart.
Toggle
Pass
Toggle changes state on pointer up; sliding off cancels.
Fail
Toggle flips on pointer down with no way to cancel.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document interaction guidelines: activate on pointer up, provide undo for destructive actions.
- List any essential down-event interactions and why they are essential.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Audit UI for pointerdown/mousedown event handlers that trigger actions.
- Move activation to click/pointerup where feasible.
- Add cancellation for drag-like interactions before pointerup.
- Add undo/confirm patterns for destructive actions.
- Ensure touch interactions allow sliding off to cancel (where appropriate).
Testing ideas
Prove conformance with evidence
- Test controls on touch devices: press then slide off and release—verify it cancels if applicable.
- Verify actions do not trigger on pointerdown unless essential.
- Check for undo/confirm on actions that can’t be safely canceled.
- Test with mouse and touch to ensure consistent behavior.
Related success criteria