Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 5 commits into from
Oct 27, 2020
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
508e736
Differentiate dragging from path-based gestures
detlevhfischer Aug 21, 2020
b225a06
Added reference to new SC 2.5.7 Dragging
detlevhfischer Aug 21, 2020
8f13ed7
Small edit
detlevhfischer Aug 21, 2020
bc1f49c
Tiny edit
detlevhfischer Aug 21, 2020
faf9dc5
Merge branch 'master' into dragging-edit
alastc Oct 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion understanding/21/pointer-gestures.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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." />
Expand Down
4 changes: 4 additions & 0 deletions understanding/22/dragging.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down