Question
Does your site or application have functionality for users to prevent or cancel an operation using a single point of contact (e.g. single taps and clicks, double-taps and clicks, long presses, and path-based gestures)?
Why is this important?
At times users may accidentally click or touch a button or target location which triggers an unwanted action. This may happen more frequently to people with tremors, mobility impairments, or cognitive disabilities. It is essential that all users have a way to prevent or undo these unintended actions.
Whom does it benefit?
Example 1
As a person with a fine motor impairment that uses a touch activated tablet,
I want the option to slide my finger off the submit button
so that I can cancel the action and not submit my assignment at that time.
Example 2
As a person with hand tremors who uses web conferencing, I sometimes hit the “end call” instead of the “mute” button.
I want the application to warn me “Are you sure you want to end the call?” before I am disconnected
so that I can verify my action before it is initiated.
What should you do?
A down-event is when a user pushes down on a mouse button or touches down on a surface, or presses down a key. Avoid activating a function when a down-event is triggered.
Ensure functionality occurs when the user triggers an up-event by releasing the pressed mouse button, lifting a finger or pointer, or releasing a key. Also ensure the user can cancel the action before the up-event occurs (e.g. slide their finger off the target without lifting up) or undo it afterwards.
How do you do it?
When a user interacts with a screen by clicking, tapping, and pressing make sure at least one is true:
- No down-event:
Avoid initiating an action to happen when the user presses or clicks a down-event. If essential, provide some other way for the user to cancel the action.
- Up-event abort or undo:
Initiate action on the up-event and a way to abort the function before completion or to undo the function after completion.
- Up reversal:
The up-event reverses any outcome of the preceding down-event (e.g. the user touches down on the wrong button, he/she can slide their finger or pointer off that button before lifting it. This will cancel the action.)
Need technical guidance?
Technical guidance is available for implementing this Success Criterion at the Understanding Success Criterion 2.5.2: Pointer Cancellation page.
Additional Resources to help you