Level AOperableNew in 2.1
2.5.2

Pointer Cancellation

Actions should fire when you lift your finger, not the moment you touch down, so you can slide off to cancel a mistap.

In plain English

When you tap a button, it should do its thing when you lift your finger, not the instant you touch down. Why does that matter? Because people who mis-tap (common with tremors or limited dexterity) can slide their finger away before releasing to cancel a mistake. If the action fires on touch-down, there is no escape, one wrong touch and it is done.

Who this is for

  • People with tremors or motor differences, who mis-tap and need a way to back out.
  • Everyone, who occasionally touches the wrong control.

How to check and fix it yourself

Native buttons and links already do the right thing. The risk is in custom controls wired to “press” events. If you have any, switch them to fire on release:

Good: standard <button>/<a>, or custom control firing on click / up-event.
Bad:  a control wired to mousedown/touchstart that fires the instant you touch.

Where we can help

This one hides inside custom JavaScript controls. We test your interactive elements to confirm they fire on release (and can be cancelled), not on touch-down. It is a subtle item on the common failures list.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Frequently asked questions

What does pointer cancellation require?+

Success Criterion 2.5.2 (Level A, added in WCAG 2.1) says that for single-pointer actions, the action should not complete on the down-event. Either it completes on the up-event, or there is a way to abort or undo it. This lets someone who presses the wrong control slide off before releasing to cancel.

Why does firing on touch-down cause problems?+

People with tremors or limited motor control often tap the wrong spot. If the action fires the instant they touch, they can't recover. If it fires on release, they can slide their finger away first to cancel, a small mercy that prevents accidental purchases or deletions.

How do I comply?+

Use native HTML buttons and links, which already activate on the up-event by default. Problems mostly appear in custom controls wired to mousedown/touchstart, switch those to fire on click or the up-event instead.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 2.5.2?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit