Draft technique "Not relying on path or multipoint gestures for operation"

[detlevhfischer]

I have drafted a simple general technique for 2.5.1 "Not relying on path or multipoint gestures for operation" that may be valuable for people planning to embed third-party stuff and wanting to check it for pointer accessibility (among other criteria).

Github link: https://github.com/w3c/wcag/blob/tech-no-reliance-on-path-or-multipoint/techniques/general/no-reliance-on-path-or-multipoint-gestures.html

View rendered in GitHack: https://raw.githack.com/w3c/wcag/tech-no-reliance-on-path-or-multipoint/techniques/general/no-reliance-on-path-or-multipoint-gestures.html

[goetsu]

This draft raise a question for me. Do the WG consider css only scrollable area requiring swipe (https://css-tricks.com/pure-css-horizontal-scrolling/ or https://css-tricks.com/practical-css-scroll-snapping/ for example) as a case where pointure gesture apply or not ? If yes the technique need to explicitly exclude this case from the scope.

[mraccess77]

Generally desktop browsers makes these areas scrollbar with the keyboard when a focusable control is in the area -- and Firefox in the past would actually dynamically add tabindex 0 to the container as well. But if you want support mobile user agents then this is a good question.

[detlevhfischer]

@goetsu This is (the draft of) a sufficient technique that ensures, by avoidance of functions that require path-based gestures, that you meet the SC. Your question is relevant, but whether scrollable areas would fail the SC does not need to be covered in this Technique, I think.

[patrickhlauke]

FWIW scrolling with touch (and not just for scrollable areas, but for the entire page itself) is not a gesture that's handled by the content, but the browser/user agent. so in my view this would not be a failure of the SC ... it's out of scope

(and yes, this discussion here is about one particular technique...not about the SC itself)

[alastc]

The example of the native horizontal scrolling will be included in the survey question that should resolve #522

[detlevhfischer]

@alastc did this ever get resolved?

Am I correct that there is agreement that scrollable areas with CSS overflow (like page scrolling or panning) are outside the scope of 2.5.1 (and now also 2.5.7)?