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.
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
WCAG2ICT Project: Add from WCAG 2.2 - 2.5.7 Dragging Movements #39
Comments
dragging movement
Seems that there will be no interpretation needed for this definition, which would apply as written. |
dropping this here, but: the one aspect of 2.5.7 that will cause/is already causing confusion is the
and
part. For web content, there's a nice clean(ish) distinction between dragging gestures that are used to operate the browser (like scrolling) and ones that are implemented on the content itself (e.g. a custom-built scroller using JavaScript). the distinction is a bit academic at times, but generally the idea is that if it's a dragging gesture to operate the browser, then it's the browser/OS that needs to provide a solution, so not a content author's responsibility. whereas something like a custom scroller is under the control of the author, so they are on the hook. this distinction falls away when we come to things like native applications, where there is no user agent. all of a sudden, in theory anyway, any interaction like scrolling is pretty much "custom". for WCAG when it comes to web content, the WG was able to sidestep this particular discussion, but native apps will have to grapple with it. |
See for instance this (split, unfortunately) thread on mastodon https://mas.to/@deanbirkett/110643436599576759 |
@patrickhlauke In WCAG2ICT, "user agent" is defined as follows:
So from a document perspective, there is a user agent that is used to render the document. The document itself doesn't provide the scroll bars/scrolling capabilities. The user agent does. |
I'm not worried from a "document" perspective. Worried from a "native application" perspective (e.g. an iOS/Android app) |
@maryjom Not sure how to do the PR request but the text is pasted here and also attached as a word doc This applies directly as written and as described in Intent from Understanding Success Criterion 2.5.7 (also provided below), replacing "user agent" with "user agent or platform software" and replacing “Web content” with “non-web documents or software”. All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the [user agent or platform software] and not modified by the author. Intent
|
Set up a survey for 2.5.7 Dragging Movements due 1 November. Created the draft in markdown using PR #245. |
As of the 9 November meeting, the TF made a resolution to incorporate the 2.5.7 content and as-is and also made a resolution to incorporate 'dragging movements' term to the "Applies to all Tech" section. |
Dragging movements has been approved by the AG WG in the review that ended 12 December. As a result of their review we adjusted the notes. This work is done. |
The text was updated successfully, but these errors were encountered: