- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 21 Apr 2016 22:41:06 +0100
- To: "White, Jason J" <jjwhite@ets.org>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
On 21/04/2016 21:20, White, Jason J wrote: > Are you envisaging that the mechanism would be implemented by a > script in the content rather than in the user agent? If so, then > having techniques for visually disclosing text alternatives in a > touch screen user interface could indeed be valuable. If it should > instead be implemented at the user agent level then it's outside the > scope of this working group, though it would of course simplify the > task for content authors, since providing the text alternative via > standard HTML or SVG elements would be enough to make it visually > available to users who request it (using a hover state in the case of > a pointing device, or using whatever convention is arrived at for > touch screen devices). My preference would initially be something relating to UAAG, but as the likelihood of UAs implementing something so arguably niche is small, a script-based technique could work. > I thought there might already be a touch counterpart to hover, in > which case it could readily be used for this purpose. There isn't (with a few minor exceptions, such as certain stylus implementations on certain devices, like the Galaxy Note II) 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 Thursday, 21 April 2016 21:41:24 UTC