Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Pointer gestures #61
Current versions of SC and Definitions
All functionality can be operated with a single untimed pointer gesture unless a multipoint or timed gesture is essential.
Note: This requirement applies to web content which interprets pointer gestures (i.e. this does not apply to gestures that are required to operate the user agent or assistive technology).
Suggestion for Priority Level (A/AA/AAA)
Related Glossary additions or changes
What Principle and Guideline the SC falls within.
Principle 2, new Guideline "Pointer Accessible"
It may not always be possible for users to perform specific gestures (e.g. draw a complex path with their finger on a touchscreen) in a precise and timely manner - they may lack the precision/accuracy/speed necessary. Further, it may not always be possible for users to perform multi-pointer gestures (e.g. a two-finger pinch/zoom, three-finger rotation). Authors must ensure that their content/functionality can be operated without requiring the user to perform timed or complex gestures.
Note: this does not preclude the inclusion of gesture-based interactions; however, if gesture-based controls are used, then an alternative which only requires a single activation/tap must be present.
Users who cannot (accurately) perform complex or timed pointer gestures (such as touchscreen swipes or multi-pointer gestures such as a two-finger pinch/zoom) will be able to operate content/functionality.
Manual test: if a web site/application has controls that accept complex or timed pointer gestures, ensure that the functionality can be operated via alternative simple controls that can be activated by a simple pointer gesture (such as tapping or a mouse click).
Do not rely solely on complex pointer gestures that require high precision or specific timings; do not rely on multi-pointer gestures; provide alternatives that do not require complex gestures (e.g. additional visible controls that perform the same function as a complex gesture and can be activated by a simple pointer gesture (mouse click, tap).
[Note: the techniques M3 and M9 are related and may be combined in 2.1. M3 requires that functionality work without timing or multi gestures, M9 requires it works without tilt, specific pressure, or angle, etc...]
This appears clear and testable to me.
I guess it would fail the current google maps interface on mobile? I can't see a means of zooming out or rotating the screen without multi-point gestures... they would have to add buttons for that to pass? Or provide a setting/mode that adds buttons for those functions.
I'm trying to relate this principle to what exists for keyboard on the desktop.
While an OS can provide ways to define "macros" for common gestures, this option is not pervasive on all touch-enabled platforms. Moreover, this may work for standard gestures that a user can predefine, but won't work for arbitrary gestures.
@alastc yes the current maps implementation would fail this, as there should be some way (which can well be something enabled in settings) to achieve rotation/zoom (and possibly even pan?) with single pointer interactions
If someone meets 2.1.1 they would also meet this, in it's current form. Perhaps it needs something like.
This has no SC manager... I can submit this proposal. Time is running out.
This was referenced
Apr 6, 2017
A few comments and questions: