-
Notifications
You must be signed in to change notification settings - Fork 283
/
Copy pathmotion-actuation.html
76 lines (69 loc) · 5.64 KB
/
motion-actuation.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="UTF-8" />
<title>Understanding Motion Actuation</title>
<link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove" />
</head>
<body>
<h1><strong>Motion Actuation</strong>
<br />
Understanding SC 2.6.1
</h1>
<section id="intent">
<h2>Intent of this Success Criterion</h2>
<p>The intent of this success criterion is to ensure that functions that are triggered by moving a device (for example, shaking or tilting) or by gesturing towards the device (so that sensors like a camera can pick up and interpret the gesturing), can also be operated by more conventional user interface components, unless the motion is essential for the function or not using motions or gestures would invalidate the activity.</p>
<p class="note">This criterion concerns input through sensors which respond directly to motions such as gesturing towards, tilting or shaking a device. It does not cover the movement of users through space as registered by geolocation sensors or beacons, or events observed by the device other than intentional gesturing by the user. It also does not cover indirect motion associated with operating a keyboard, pointer, or assistive technology.</p>
<p>Devices often have sensors that can act as inputs, such as accelerometer and gyroscope sensors on a phone or tablet device. These sensors can allow the user to control something by simply changing the orientation or moving the device in particular ways. In other situations, web content can interpret user gestures via the camera or other sensors to actuate functions. For example, shaking the device might issue an "Undo" command, or a gentle hand wave might be used to move forward or backward in a sequence of pages. Some users with disabilities are not able to operate these device sensors (either not at all, or not precisely enough) because the device is on a fixed mount (perhaps a wheelchair) or due to motor impairments. Functionality must be implemented in a way that other or additional means of activation are available.</p>
<p>In addition, some users may accidentally activate sensors due to tremors or other motor impairments. The user must have the ability to turn off motion actuation to prevent such accidental triggering of functions. Applications may be able to meet this requirement by using an <a href="../conformance.html#accessibility-support">accessibility supported</a> operating system settings which allows the user to disable motion detection.</p>
<p>Some applications are specifically created to use device sensor data. Examples of content that are exempt from this requirement include a pedometer that relies on device motion to count steps.</p>
<section id="benefits">
<h3>Benefits</h3>
<ul>
<li>This Success Criterion helps people who may be unable to perform particular motions (such as tilting, shaking, or gesturing) because the device may be mounted or users may be physically unable to perform the necessary movement. This success criterion ensures that users can still operate all functionality by other means (e.g., touch or voice input).</li>
<li>Other users may benefit in situations where they are unable to hold and move the device because their hands are occupied with some other activity.</li>
</ul>
</section>
</section>
<section id="examples">
<h2>Examples of Success Criterion 2.6.1</h2>
<ul>
<li>After text has been entered in an input field, shaking a device shows a dialog offering users to undo the input. A cancel button next to the text field offers the same functionality.</li>
<li>A user can tilt a device to advance to the next or a previous page. Buttons or links are also provided to perform the same function.</li>
<li>A user can move or pan a device to change the view in an interactive photo. A control is also available to perform these same functions.</li>
<li>A user can gesture towards the device to navigate content. Controls are also available to navigate.</li>
<li>A user can choose an application setting which turns off Shake to Undo features.</li>
</ul>
</section>
<section id="resources">
<h2>Related Resources</h2>
<ul>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/API/Detecting_device_orientation">Detecting device orientation</a></li>
<li><a href="https://developer.mozilla.org/en-US/docs/Web/API/DeviceMotionEvent">DeviceMotionEvent</a></li>
</ul>
</section>
<section id="techniques">
<h2>Techniques</h2>
<section id="sufficient">
<h3>Sufficient</h3>
<ul>
<li>GXXX: Not using the devicemotion event to activate content functionality</li>
<li>GXXX: Ensuring that alternative means of input exist when using device motion sensor input to activate content functionality</li>
<li>GXXX: Providing an application setting to disable motion actuation</li>
<li>GXXX: Supporting system level features which allow the user to disable motion actuation</li>
</ul>
</section>
<section id="advisory">
<h2>Advisory</h2>
</section>
<section id="failure">
<h2>Failure</h2>
<ul>
<li>FXXX: Failure of Success Criterion 2.5.4 due to functionality that can only be activated via devicemotion events (e.g., shaking or tilting)</li>
<li>FXXX: Failure of Success Criterion 2.5.4 due to an inability to disable motion actuation</li>
<li>FXXX: Failure of Success Criterion 2.5.4 due to disrupting or disabling system level features which allow the user to disable motion actuation</li>
</ul>
</section>
</section>
</body>
</html>