Skip to content

Commit

Permalink
Update dragging-movements.html
Browse files Browse the repository at this point in the history
Finetuning the dragging movements understanding text in response to issue #1917 
- Replacing dragging motion with dragging movement
- Reducing talk about Pointer Gestures
- Simplifying examples, adding single pointer option to select a value in a radial control
  • Loading branch information
detlevhfischer authored Jul 12, 2021
1 parent 1005e03 commit 98e976c
Showing 1 changed file with 8 additions and 13 deletions.
21 changes: 8 additions & 13 deletions understanding/22/dragging-movements.html
Original file line number Diff line number Diff line change
Expand Up @@ -35,24 +35,19 @@ <h2>Intent of Dragging Movements</h2>

<p>Some people cannot perform dragging motions in a precise manner. Others use a specialized or adapted input device such as a head pointer, eye-gaze system, or speech-controlled mouse emulator, which makes dragging cumbersome, error-prone, or outright impossible.</p>

<p>When an interface implements functionality that uses dragging motions, some users can tap or click, but not accurately maintain contact whilst performing a dragging motion. An alternative method must be provided so that users with mobility impairments that use a pointer (mouse, pen, or touch contact) can use the functionality.</p>
<p>When an interface implements functionality that uses dragging movements, some users can tap or click, but not accurately maintain contact whilst performing the movement. An alternative method must be provided so that users with mobility impairments who use a pointer (mouse, pen, or touch contact) can use the functionality.</p>

<p>Success Criteria 2.1.1 Keyboard and 2.1.3 Keyboard (No Exception) require dragging features to be keyboard accessible; however, it is possible to create an interface that works with dragging and keyboard controls that does not work using only clicks or taps.</p>

<p>This Success Criterion applies to dragging motions as opposed to pointer gestures, which are covered in Success Criterion 2.5.1 Pointer Gestures. Pointer gestures include directional path-based as well as multi-point gestures. In contrast, for dragging motions, only the start and end point of the motion matters, not the actual path.</p>
<p>This Success Criterion applies to dragging movements as opposed to pointer gestures, which are covered in Success Criterion 2.5.1 Pointer Gestures. Pointer gestures include directional path-based as well as multi-point gestures. In contrast, for dragging movements, only the start and end point of the movement matters, not the actual path.</p>

<p>There may be cases where a dragging movement is essential, for example, drawing a freeform figure, or playing a game where the aim is to follow a particular track as accurately as possible. The criterion has an exception for these cases where the task requires dragging.</p>
<p>There may be cases where a dragging movement is essential, for example, drawing a freeform figure, or playing a game where the aim is to follow a particular track as accurately as possible. The criterion has an exception for these cases.</p>

<p>Some tasks may typically involve dragging, such as sorting items in a list, but as there are other ways to achieve that task they are not considered essential.</p>

<h3>Distinguishing dragging movements from path-based pointer gestures</h3>

<p>Dragging movements covered in this Success Criterion are pointer interactions where only the endpoints matter. Once the pointer engages with a target, the direction of the dragging motion does not factor into the interaction until the pointer disengages the target. Since the dragging movement does not have an intermediate point, the dragging motion can go in any direction.</p>

<p>Path-based gestures covered in Success Criterion 2.5.1 Pointer Gestures are pointer interactions that involve at least an initial directionality. The pointer motion must include at least one intermediate point to qualify as a path-based gesture. The intermediate point defines the motion as a gesture by requiring a specific path, even when the entire path to complete the interaction is not predefined. While a user may use dragging movements to perform the interaction, path-based gestures requires following a path to an intermediate point. For more details, refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html">Understanding Success Criterion 2.5.1 Pointer Gestures</a>.</p>



<p>Dragging movements covered in this Success Criterion are pointer interactions where only the endpoints matter. Once the pointer engages with a target, the direction of the dragging motion does not factor into the interaction until the pointer disengages the target. Since the dragging movement does not have an intermediate point, the dragging motion can go in any direction. Path-based gestures covered in Success Criterion 2.5.1 Pointer Gestures. For more details, refer to <a href="https://www.w3.org/WAI/WCAG21/Understanding/pointer-gestures.html">Understanding Success Criterion 2.5.1 Pointer Gestures</a></p>

</section>
<section id="benefits">
Expand All @@ -65,13 +60,13 @@ <h2>Benefits of Dragging Movements</h2>
</section>

<section id="examples">
<h2>Examples of Dragging Movements</h2>
<h2>Examples of Dragging Movements with alternatives</h2>

<ul>
<li>A sortable list of elements may, after focussing a list element, provide adjacent controls for moving the element up or down in the list by simply tapping/clicking on those controls.</li>
<li>In a sortable list, when a list item is activated by tapping or focusing, adjacent arrows pointing up and down are shown. Users can move the selected list item up or down the list simply b< tapping/clicking on those arrows.</li>
<li>A kanban implementation may provide an additional pop-up menu for focused elements that can be activated by simple clicks/taps providing an option for moving the selected element to another kanban silo.</li>
<li>A radial control widget where the value can be set by dragging includes a text field that presents the current value and offers the input of the desired value via a keyboard (including on-screen virtual keyboards).</li>
<li>A map allows users to drag the view of the map around, and the map has up/down/left/right buttons to move the view as well.</li>
<li>A radial control widget where the value can be set by dragging includes a text field that presents the current value and offers the input of the desired value via a keyboard (including on-screen virtual keyboards). In addition, a value can also be set by directly tapping or clicking an any point in the radial control,</li>
<li>A map allows users to drag the view of the map around. The map also shows up/down/left/right buttons to move the view in a stepwise fashion.</li>
</ul>

</section>
Expand Down

0 comments on commit 98e976c

Please sign in to comment.