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

Jump to bottom

"single-pointer" definition should not include path-based gestures in 2.5.1, 2.5.2, and 2.5.7 #3535

Closed
philljenkins opened this issue Nov 6, 2023 · 5 comments · Fixed by #3536
Closed

"single-pointer" definition should not include path-based gestures in 2.5.1, 2.5.2, and 2.5.7 #3535

philljenkins opened this issue Nov 6, 2023 · 5 comments · Fixed by #3536

Comments

@philljenkins
Copy link

philljenkins commented Nov 6, 2023 •
edited
Loading

The definition of "single-pointer" incorrectly includes "path-based gestures", which it should not since "path-based gestures" by definition are dragging.

https://www.w3.org/WAI/WCAG22/Understanding/dragging-movements.html#dfn-single-pointer

single-pointer: pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures

This fails to make sense when replacing the definition for the term in the SC

2.5.7 ... can be achieved by a [pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures] without dragging,

also fails where it's using a circular definition in the SC

2.5.1 ... path-based gestures for operation can be operated with a [pointer input that operates with one point of contact with the screen, including single taps and clicks, double-taps and clicks, long presses, and path-based gestures] without a path-based gesture, unless ...

"path-based gestures can be operated with a path-based gesture without a path-based gesture"

Removing the "path-based gestures" from the definition of "single-pointer" would solve the problem in the following documents:

WCAG 2.1 single-pointer definition
Understanding 2.1
2.5.1 Pointer Gestures
2.5.2 Pointer Cancellation

WCAG 2.2 single-pointer definition
Understanding 2.2
2.5.1 Pointer Gestures
2.5.2 Pointer Cancellation
2.5.7 Dragging Movement
@philljenkins philljenkins changed the title 2.5.8 & 2.5.1 "single-pointer" definition should not include path-based gestures 2.5.1 & 2.5.7 "single-pointer" definition should not include path-based gestures Nov 6, 2023
@philljenkins philljenkins changed the title 2.5.1 & 2.5.7 "single-pointer" definition should not include path-based gestures "single-pointer" definition should not include path-based gestures in 2.5.1, 2.5.2, and 2.5.7 Nov 6, 2023
@philljenkins philljenkins mentioned this issue Nov 6, 2023
Closed
@philljenkins
Copy link
Author

  • Apple defines "Standard Gestures" as: Tap, Swipe, Drag, Touch (or pinch) and hold, Double tap, Zoom, and Rotate
  • In addition to the standard gestures supported in all platforms, iOS and iPadOS support a few other gestures that people expect: Three-finger swipe, Three-finger pinch, Four-finger swipe (iPadOS only)
  • visionOS defines two types of gestures: indirect and direct. Direct gestures include: Touch, Touch and hold, Touch and drag, Double touch, Swipe, With two hands, pinch and drag together or apart, With two hands, pinch and drag in a circular motion.

@patrickhlauke
Copy link
Member

this goes back to the historically borked way for some reason 2.1 decided to define "single pointer" not to mean the actual pointer itself, but the action of using a single pointer...

@patrickhlauke
Copy link
Member

xref #749 (comment)

@patrickhlauke
Copy link
Member

if we want to fix this, i'd propose removing mentions of taps, clicks, etc, and just defining/clarifying that a "single pointer" means a mouse, stylus, single finger on a touchscreen, and stands in contrast with multi-pointer/multi-touch scenarios.

patrickhlauke added a commit that referenced this issue Nov 6, 2023
@patrickhlauke
Rewrite definition for single pointer
c69c778 
The definition for "single pointer" has had issues for a long time, as it mixes the idea of what is a pointer with the action(s) *performed* using a pointer.

See #749 (comment) and the recent #3535 where this is once again causing a non-sequitur
@patrickhlauke patrickhlauke mentioned this issue Nov 6, 2023
Merged
@patrickhlauke
Copy link
Member

Trying once more to move this definition away from interactions, and to just define what a "single pointer" actually is #3536

alastc added a commit that referenced this issue Mar 11, 2024
@patrickhlauke @alastc
Update definition for single pointer (#3536)
a9dbe11 
The definition for "single pointer" has had issues for a long time, as
it mixes the idea of what a pointer *is* with the action(s) *performed*
using a pointer.

I originally tried to fix this, but there was no appetite for it once
2.1 was released. However, with 2.2 and the new 2.5.7 Dragging Movement
SC, the broken definition is causing actual misunderstandings/illogical
non-sequiturs.

See #749 (comment) and
the recent #3535 where this is once
again causing a non-sequitur

Closes #3535

(this is effectively a follow-up to #809
which had disambiguated things, but the definition had since been
changed further/again to reintroduce the ambiguous wording we have at
this point which confuses input with action)

This would be applied to WCAG 2.1 and 2.2, unless there is a decision to
only apply it to 2.2.

EDIT: Also closes #394


<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/3536.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Preview</a> |
<a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3536/afbf9ee...6c36df1.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Diff</a>

---------

Co-authored-by: Alastair Campbell <[email protected]>
kfranqueiro pushed a commit that referenced this issue Dec 18, 2024
@patrickhlauke @kfranqueiro
Update definition for single pointer (#3536)
04038fc 
The definition for "single pointer" has had issues for a long time, as
it mixes the idea of what a pointer *is* with the action(s) *performed*
using a pointer.

I originally tried to fix this, but there was no appetite for it once
2.1 was released. However, with 2.2 and the new 2.5.7 Dragging Movement
SC, the broken definition is causing actual misunderstandings/illogical
non-sequiturs.

See #749 (comment) and
the recent #3535 where this is once
again causing a non-sequitur

Closes #3535

(this is effectively a follow-up to #809
which had disambiguated things, but the definition had since been
changed further/again to reintroduce the ambiguous wording we have at
this point which confuses input with action)

This would be applied to WCAG 2.1 and 2.2, unless there is a decision to
only apply it to 2.2.

EDIT: Also closes #394

<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/3536.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Preview</a> |
<a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3536/afbf9ee...6c36df1.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Diff</a>

---------

Co-authored-by: Alastair Campbell <[email protected]>
(cherry picked from commit a9dbe11)
kfranqueiro pushed a commit that referenced this issue Dec 18, 2024
@patrickhlauke @kfranqueiro
Update definition for single pointer (#3536)
dda3649 
The definition for "single pointer" has had issues for a long time, as
it mixes the idea of what a pointer *is* with the action(s) *performed*
using a pointer.

I originally tried to fix this, but there was no appetite for it once
2.1 was released. However, with 2.2 and the new 2.5.7 Dragging Movement
SC, the broken definition is causing actual misunderstandings/illogical
non-sequiturs.

See #749 (comment) and
the recent #3535 where this is once
again causing a non-sequitur

Closes #3535

(this is effectively a follow-up to #809
which had disambiguated things, but the definition had since been
changed further/again to reintroduce the ambiguous wording we have at
this point which confuses input with action)

This would be applied to WCAG 2.1 and 2.2, unless there is a decision to
only apply it to 2.2.

EDIT: Also closes #394

<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/3536.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Preview</a> |
<a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3536/afbf9ee...6c36df1.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Diff</a>

---------

Co-authored-by: Alastair Campbell <[email protected]>
(cherry picked from commit a9dbe11)
kfranqueiro pushed a commit that referenced this issue Dec 19, 2024
@patrickhlauke @kfranqueiro
Update definition for single pointer (#3536)
b61e772 
The definition for "single pointer" has had issues for a long time, as
it mixes the idea of what a pointer *is* with the action(s) *performed*
using a pointer.

I originally tried to fix this, but there was no appetite for it once
2.1 was released. However, with 2.2 and the new 2.5.7 Dragging Movement
SC, the broken definition is causing actual misunderstandings/illogical
non-sequiturs.

See #749 (comment) and
the recent #3535 where this is once
again causing a non-sequitur

Closes #3535

(this is effectively a follow-up to #809
which had disambiguated things, but the definition had since been
changed further/again to reintroduce the ambiguous wording we have at
this point which confuses input with action)

This would be applied to WCAG 2.1 and 2.2, unless there is a decision to
only apply it to 2.2.

EDIT: Also closes #394

<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/3536.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Preview</a> |
<a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3536/afbf9ee...6c36df1.html"
title="Last updated on Mar 8, 2024, 7:30 PM UTC (6c36df1)">Diff</a>

---------

Co-authored-by: Alastair Campbell <[email protected]>
(cherry picked from commit a9dbe11)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update definition for single pointer w3c/wcag
2 participants
@patrickhlauke @philljenkins