Disambiguation of path-based gesture versus dragging movement#4843
Open
patrickhlauke wants to merge 21 commits intomainfrom
Open
Disambiguation of path-based gesture versus dragging movement#4843patrickhlauke wants to merge 21 commits intomainfrom
patrickhlauke wants to merge 21 commits intomainfrom
Conversation
* Remove the confusing "intermediate"/"midpoint" patch that was added mostly as a way to retcon/patch in applicability to sliders/carousels into pointer gestures, once the normative wording was already baked in and it turned out to be too difficult to make it apply to dragging sliders. * Emphasise that for gestures, the end-point (and sometimes even the start-point) don't actually matter so much as the direction (and potentially speed) * Repurpose the "wiggly line from point 1 to point 2" to actually illustrate dragging movement, and move the two illustrations (straight line and wiggly line) to the section that tries to explain the difference between dragging and path-based gestures * Use some consistency: start-point and end-point (not "start point", or "endpoint" etc, it was all a bit mix and match before)
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
Author
This was referenced Dec 31, 2025
patrickhlauke
force-pushed
the
patrickhlauke-pointer-gesture-dragging-disambiguation
branch
from
602b611 to
446449e
Compare
…but dragging movements
patrickhlauke
changed the title
Contributor
|
Looks very solid, great work, @patrickhlauke |
detlevhfischer
approved these changes
Jan 2, 2026
Contributor
detlevhfischer
left a comment
detlevhfischer
left a comment
There was a problem hiding this comment.
Just some editorial comments - the substance is there.
Member
Author
thank you @detlevhfischer ... good to get some more of the cruft (most of it was existing text I think) out of those docs. I'll have a look through and make tweaks |
…ord them for more clarity
fstrr
reviewed
Jan 6, 2026
Co-authored-by: Francis Storr <francis.storr@intel.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is a long-overdue disambiguation that removes the half-hearted (half-a**ed) retconning attempt to make pointer gestures apply to sliders at the time before we had dragging movements. (yes, this may mean that for 2.1, sliders MAY not be covered by pointer gestures anymore, but even with the additions we had, they weren't per se...so this doesn't actually change anything normatively in my mind, other than remove the weird points of overlap and confusion).
In understanding for pointer gestures:
Preview: https://deploy-preview-4843--wcag2.netlify.app/understanding/pointer-gestures
In understanding for dragging movements:
Preview: https://deploy-preview-4843--wcag2.netlify.app/understanding/dragging-movements
Closes #3344
Supersedes #3148
Closes #2684