Closed patrickhlauke closed 1 week ago
Name | Link |
---|---|
Latest commit | a79bb49c2c3761b349f3539cd2a3553175d2e1bc |
Latest deploy log | https://app.netlify.com/sites/wcag2/deploys/66edd658cbbc860008df3683 |
Deploy Preview | https://deploy-preview-4070--wcag2.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
to be clearer: a tap, a swipe, a path-based gesture is not a "single pointer". they are examples of gestures performed using a single pointer
just on the point about "mechanism" having a different meaning in WCAG - note we already have an SC (albeit at AAA) that uses "mechanism" in the exact way it's intended here - 2.5.6 Concurrent Input Mechanisms
Although in the longer prose for the SC, it switches to "input modalities" ... so, maybe "modality" here as well, rather than mechanism? would that help?
if, contrary to the original consensus position, we were to expand the informative note, maybe something like this could strike the correct balance:
<p class="note">In contrast to single pointer interactions – including clicks, taps, dragging motions, and single-finger swipe gestures – multipoint interactions involve the use of two or more pointers at the same time – such as two finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.</p>
as this then gives dragging etc only as examples, so hopefully avoids the non-sequitur we saw in https://github.com/w3c/wcag/issues/394
I'd suggest this to reduce the sentence complexity:
single pointeran input that only targets a single point on the page/screen at a time – such as a mouse, single finger on a touch screen, or stylus.
Single pointer interactions include clicks, taps, dragging motions, and single-finger swipe gestures. In contrast, multipoint interactions involve the use of two or more pointers at the same time, such as two finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.
Reviewed and finalized on Sep 20 TF call. Returned to the Errata for CFC column.
Follow-up to https://github.com/w3c/wcag/pull/3536#issuecomment-2352336750 to potentially address concerns by @WilcoFiers @dbjorge
Tries to more clearly differentiate "input" as in the modality from the gestures/interactions that are the result of using a particular input modality
Preview | Diff