Intent
The intent of this success criterion is to make it easier for users to prevent accidental or erroneous pointer input. People with various disabilities can inadvertently initiate touch or mouse events with unwanted results.
There is a distinction between when someone touches a screen and when they remove their finger. Similarly, in mouse interaction, there is a difference between pressing and releasing the mouse button. When activation occurs only when the pointer is released, users have the opportunity to prevent (cancel) the activation. They can move their finger or other pointer (e.g., the mouse cursor) away from the target when they realise that they touched that target inadvertently or erroneously.
Up-event activation refers to the activation of a target when the pointer is released. In a touchscreen interaction, when the finger touches a target, the up-event activation ony occurs when the finger is lifted while still being within the target boundary. Similarly in mouse interaction, the up-event occurs when the mouse button is released while the cursor is still within the boundary of the initial target when the mouse button was pressed.
Authors can reduce the problem of users inadvertently triggering an action by using generic platform activation/click events that activate functionality on the up-event. For example, the "click" event in JavaScript triggers on release of the primary mouse button, and is an example of an implicit up-event. Despite its name, the onclick event handler works both for mouse interaction as well as for touch interaction.
If activation on the down-event is necessary, there are several options:
- There is a mechanism to abort the function before completion. An example is a drag-and-drop behaviour where the activation starts on the down-event but is cancelled when the picked-up target is released outside a valid drop target.
- A confirmation dialog or an undo button allows the user to reverse / undo the action.
- A setting in preferences allows the user to choose whether activation happens on the down-event or the up-event.
Examples of where the timing of an activation is essential and requires the down-event would be:
- An activity that would be invalid if activation waited for the up-event, such as when playing an on-screen piano keyboard.
- A program for shooting skeets where waiting for the "up" event would invalidate the activation.
Benefits
- Makes it easier for all users to recover from hitting the wrong target.
- Helps people with visual disabilities, cognitive limitations, and motor impairments by reducing the chance that a control will be accidentally activated or an action will occur unexpectedly.
- Individuals who are unable to detect changes of context are less likely to become disoriented while navigating a site.
Examples
- For interface elements that have a single tap or long press as input, the corresponding event is triggered when the finger is lifted inside that element.
- A phone dialling application has number keys that are immediately activated on touch (i.e. via the down-event). A user can undo an unwanted number input by hitting the backspace button to delete the erroneous digit.
- A drag-and-drop interface allows users to sort vertically stacked cards by picking up one card with the pointer (down-event), move it to a new position, and insert it at the new location when the pointer is released (up-event). Releasing the pointer outside the drop target area reverts the action, i.e., it moves the card back to the old position before the interaction started.
Related Resources
Resources are for information purposes only, no endorsement implied.
- Resource
Techniques
Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, particularly the "Other Techniques" section.
Sufficient Techniques
Select the situation below that matches your content. Each situation includes techniques or combinations of techniques that are known and documented to be sufficient for that situation.
Situation
- Activating a control using the up-Event in HTML, iOS and Android
- M029(wiki) Touch events are only triggered when touch is removed from a control
Advisory Techniques
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.
Failures
The following are common mistakes that are considered failures of this Success Criterion by the WCAG Working Group.
Key Terms
new
platform event that occurs when the trigger stimulus of a pointer is depressed
The down-event may have different names on different platforms, such as "touchstart" or "mousedown".
if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform
processes and outcomes achievable through user action
process or technique for achieving a result
The mechanism may be explicitly provided in the content, or may be relied upon to be provided by either the platform or by user agents, including assistive technologies.
The mechanism needs to meet all success criteria for the conformance level claimed.
new
pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures
new
platform event that occurs when the trigger stimulus of a pointer is released
The up-event may have different names on different platforms, such as "touchend" or "mouseup".