Skip to content

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

@philljenkins

Description

@philljenkins

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions