2.5.7 Dragging: adding reference to 2.5.1 Pointer Gestures and v.v.

understanding/21/pointer-gestures.html

@@ -21,7 +21,7 @@ <h2>Intent of this Success Criterion</h2>
 
 			<p>Examples of path-based gestures include swiping, sliders and carousels dependent on the direction of interaction, and other gestures which trace a prescribed path such as drawing a specific shape. Such paths may be drawn with a finger or stylus on a touchscreen, graphics tablet, or trackpad, or with a mouse, joystick, or similar pointer device.</p>
 
-			<p>Pointer interactions where the movement between the start and end points can go in any direction and are entirely non-prescriptive are not path-based.</p>
+			<p>Dragging motions where the movement between the start and end points can go in any direction and is entirely non-prescriptive are not path-based. Dragging motions are covered in Success Criterion 2.5.7 Dragging.</p>
 
 			<figure id="figure-path-based-gesture-2">
 				<img src="img/path-based-gesture-2.png" width="400" alt="Hand showing a starting touch, 1. Going to a second point, 2. It follows a very random path." />

understanding/22/dragging.html

@@ -37,6 +37,10 @@ <h2>Intent of Dragging Movements</h2>
 
         <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>There is already a requirement for 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>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>
 
       <h3>Distinguishing dragging movements from path-based pointer gestures</h3>