- Success Criterion 2.5.2
- Conformance level A
Button Firing on Touchstart Instead of Release
2.5.2 — Pointer Cancellation
Scenario
Setting
A pharmacy app's prescription-refill form
What’s wrong
Buttons firing on touchstart for "responsiveness", no abort possible by sliding off.
Example
A QA pass on a pharmacy app's prescription-refill form turns this up: buttons firing on touchstart for "responsiveness", no abort possible by sliding off.
Why it matters
People with tremor or imprecise pointing who need to cancel a down-press. On a pharmacy app's prescription-refill form specifically, they get stuck and can't reach the control.
How to test
Press down (touchstart) on a button and slide off before lifting: if the action already fired on touchstart, it fails.
How to fix
The action must complete on release (up-event) so the user can slide off to abort, or an abort/undo must be available.
Outcome
Fixed, a visitor to a pharmacy app's prescription-refill form can complete the task using only the keyboard.
Who is affected
People with tremor or imprecise pointing who need to cancel a down-press.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Action That Fires the Instant the Pointer Goes Down
- Drag Interaction That Commits With No Way to Cancel
- Menu That Opens and Selects on the Same Press-and-Drag
- Destructive Action Firing on Press With No Way to Abort
- Press-to-Trigger Control Where Release Confirmation Was Possible
- Custom Gesture That Commits Mid-Motion Instead of on Release