All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture. (Level A)

Rationale

Objective: Let users operate touchscreens with a simple action

The key intended beneficiaries of Pointer Gestures are users with some physical disabilities, who may lack the ability to carry out complex gestures on mobile devices or other touchscreens. When authors create a custom gesture, they need to ensure it is a simple action using a single contact point or that there is a simple action to achieve the same result.

An example of a multipoint gesture is a two-finger pinch to zoom. An example of a path-based gesture is a swipe up (since the direction of the swipe -- its path -- determines the interpreted action).

Note: This checkpoint does not apply to operating system and browser gestures, which are not under the author's control. Most devices have OS-level accessibility features which offer alternatives for device-based complex gestures.

Essential Exception: Multipoint or patterned gestures (e.g., that require the drawing of a specific shape) are allowed if that is the only way to achieve something, such as a users's signature. Note that in many cases a signature may not be essential if there are other acceptable ways to, for instance, validate a user's identify or capture their consent.

Refer to Understanding 2.5.1 for more information (external link to WCAG).

Development Techniques

This paragraph appears generically in all checkpoints. Review the General techniques as well as other tabs applicable to your technology.  Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General techniques

TAny item in this section represents a technique deemed sufficient. Ensure you review WCAG Common Failures to avoid development mistakes.

Web (HTML, ARIA, CSS) techniques

In addition to the General techniques, any item in this section represents a technique deemed sufficient.

Mobile Native (iOS) techniques

There are no specific Mobile Native iOS techniques for this checkpoint. Refer to the General techniques section.

Eclipse techniques

There are no specific Eclipse techniques for this checkpoint. Refer to the General techniques section.

Windows-based (MSAA+IA2) techniques

There are no specific Windows-based (MSAA+IA2) techniques for this checkpoint. Refer to the General techniques section.


Many links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation 05 June 2018: http://www.w3.org/TR/WCAG21/

Copyright © 1994-2019 World Wide Web Consortium, ( Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.

Copyright © 2019 IBM Corporation