James Craig

> @cookiecrook for the case of DocuSign, can you think of a different behavior that you'd want to enable with any existing AT and a mode other than touch? For...

@minorninth wrote: > @cookiecrook for the case of DocuSign, can you think of a different behavior that you'd want to enable with any existing AT and a mode other than...

I haven't considered fully, but there may be a case for multiple mix-and-match values, and an `all` value (equivalent to direct). I'm not certain how the implementations would differ though,...

> Having a distinction between only one finger and multi-finger requirements would probably be useful. If an area requires multi-fingers, other system wide gestures have to be ignored. Good point....

@ckundo wrote: > dragging and transforming objects in a 2D or 3D canvas context. If object based (with sub-DOM notes or TBD AOM virtual notes), that could be a use...

@minorninth @carmacleod @jnurthen What do you think about `touchpassthrough`? Verbose, but definitely the most author-understandable suggestion so far.

> How about `aria-touch="passthrough"` That might prevent the single vs multi distinction. Is that a dealbreaker?

Also mentioned in the WG call: - https://www.w3.org/WAI/WCAG21/Understanding/parsing.html - https://adrianroselli.com/2022/12/the-411-on-4-1-1.html

Looks like the default value exposed by WebKit to the platform AX API is also 0. The Web Accessibility Inspector doesn't display this value, but the native Accessibility Inspector does....

Is `associationlistitemvalue` the record for longest ARIA role? Is there still time to aim for something shorter?