WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Applying 2.5.1 Pointer Gestures to tile sliders in native apps.

for

From: glen walker
Date: Apr 14, 2023 10:37AM

It's interesting that the understanding document says, "A path-based
gesture involves an interaction where not just the endpoints matter. If
going through an intermediate point also affects its meaning then it is a
path-based gesture." So a path-based gesture requires at least 3 points
and not just the endpoints.

If you think about swiping or sliding a carousel type widget, there aren't
three points involved in that process so it shouldn't be considered
path-based, based on that definition. In fact, sliding a carousel only
cares about the starting point and then which direction from that starting
point you start dragging. The actual end point of that process is somewhat
irrelevant so it doesn't really have two points in the path.

But then the understanding document says, "Examples of path-based gestures
include swiping, sliders and carousels dependent on the direction of
interaction".

That seems contradictory. They define path-based to have 3 (or more) points
in the path but then give an example of something that doesn't even have 2
points.

If the carousel had next/previous buttons at either end, in addition to
supporting swiping, then you wouldn't have a problem. But without those
buttons, does it fail 2.5.1? Based on the definition in the understanding
section, I don't think it does. Of course, the understanding section is
not normative and it's unfortunate that the definition of "path-based" is
not a link in the actual guideline because that would have made the
definition normative.