- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Mon, 11 Jul 2016 12:01:23 +0100
- To: public-mobile-a11y-tf@w3.org
FWIW I've filed an issue in WCAG's github repo about this: https://github.com/w3c/wcag/issues/201 Thoughts/support there welcome. P On 10/07/2016 17:18, Patrick H. Lauke wrote: > On 10/07/2016 17:03, Gregg Vanderheiden wrote: >> Great point Patrick >> >> There are devices that do have HOVER (detect finger near screen) — but >> not all devices do - and we can’t assume that they all will any time >> soon (or perhaps not all ever). >> >> So great reminder on this. > > So we good with this idea of, first of all, patching G183 to exclude > touchscreen interfaces (and any other interfaces that lack hover/focus)? > Should we take it straight to the WCAG WG, or work on something here > first before submitting a change proposal? > >>> In short, I'd say we should add a note to G183 saying that it does NOT >>> apply to touchscreen input (without AT), since there's generally no >>> concept of hover for touchscreen devices, and that focus is applied >>> only after the user initiated an interaction/activation. > > P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Monday, 11 July 2016 11:01:45 UTC