2.5.2 Pointer Cancellation (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.5.2 Pointer Cancellation (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.5.2 Pointer Cancellation
2.5.2 Pointer Cancellation (Level A)
What it requires: For most functions, the action fires on pointer-up (release), not pointer-down (press) — so a user can move their pointer away before releasing to cancel an accidental activation.
Common failure: A custom “Add to Cart” or menu-item button fires its action on mousedown/touchstart instead of click/touchend, so a user can’t abort an accidental press by dragging off the button before releasing.
Fix it: Bind actions to click (which natively fires on up-events with the standard cancellation behavior) rather than mousedown/touchstart, unless there’s a specific, justified reason to use down-events.
In 2.5 Input Modalities: ← 2.5.1 Pointer Gestures · 2.5.3 Label in Name →
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.