Resource guide
2.5.2 Pointer Cancellation
Functions triggered by a single pointer must not activate on the down-stroke alone, so accidental taps can be cancelled.
By Calling All Minds·Last updated April 2026
Success criterion
Conformance level
Essential baseline — must meet for any compliance.
What it means
When a function fires on the moment a pointer touches a target (the down event), there is no opportunity to cancel an accidental press. By requiring that functions activate on pointer up, or by providing another way to cancel or undo, accidental activations can be prevented.
This matters for users with tremors, motor difficulties, or anyone who may accidentally touch a target while scrolling.
In practice
Activate actions on the pointerup or mouseup event rather than pointerdown or mousedown. This is the default browser behaviour for standard buttons and links.
If you must activate on pointerdown, provide an abort or undo mechanism. The user must be able to cancel the action by moving the pointer off the target before releasing, or by a clear undo function.
Avoid attaching actions to touchstart or mousedown events for destructive or hard-to-reverse actions.
Common failures
- Button that fires its action immediately on
mousedownortouchstartwith no way to cancel - Drag-and-drop that triggers a destructive action on
pointerdownbefore the user can abort
AXS Audit
AXS Audit checks your site against 2.5.2 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.
