WCAG 2.1 · Level A · Operable
2.5.2 Pointer Cancellation
Manual verification
How to validate 2.5.2 by hand
Check when pointer actions take effect and whether the action can be cancelled or reversed.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Test click/tap controls by pressing down, moving away before release, and then releasing over and away from the target.
- Check whether activation occurs on the up-event, can be cancelled before completion, or can be undone after completion.
- Repeat for destructive, financial, and navigation actions, noting any timing that changes the outcome.
Evidence to record
Record the pointer down/up sequence, action timing, and whether cancellation or reversal is available.
Scope and exceptions
Some functions depend on the down-event, and essential actions may have an exception. Evaluate the actual event behavior and the criterion’s listed alternatives.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.