2.5.7 dragging movement understanding seems to imply alternative MUST be on same page

[patrickhlauke]

https://www.w3.org/WAI/WCAG22/Understanding/dragging-movements has a heading "Alternatives for dragging movements on the same page". This seems to imply, or strongly suggest, that the alternative MUST be on the same page. I'd question this...while not a great user experience, I don't think having an alternative on a separate page is a failure as long as the user can still achieve their end goal.

Would propose either modifying that heading, or adding some wording to explain that the "same page" part isn't normative, and that it's also fine (normatively) to provide the functionality on another page, provided that the user can reach it without using dragging movement etc

[mbgower]

IMO, there are discrete topics.

An alternative conforming version can be used with any SC to meet. In that situation, a page is failing, and the author provides a completely different version to meet. We do not normally call that out on Understanding or techniques pages, because it is a generic approach.

This section of the Dragging Movements understanding doc is specifically addressing a situation where a page can pass by achieving equivalent functionality using a single pointer without dragging on the same page (which meets the wording of the SC). There are a number of SCs that use the same principle. Some, even spell it out in SC wording, for instance Target Size. Maybe we can explain that a bit better?

[patrickhlauke]

as this caused confusion/uncertainty in a colleague's audit today, it may be worth reinforcing this in the understanding (maybe as a side note for that section)