- From: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Date: Mon, 25 Apr 2016 14:40:42 +0000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, "White, Jason J" <jjwhite@ets.org>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
> > 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) For what it's worth on native Android TalkBack appears to send hover events when explore by touch is used. In Chrome with TalkBack on Android when you double tap an element such as a paragraph of text a hover event is triggered. If you hook a mouse to an Android device and move the pointer around you will hear speech and the TalkBack cursor will move around. Jonathan Jonathan Avila Chief Accessibility Officer SSB BART Group jon.avila@ssbbartgroup.com 703.637.8957 (Office) Visit us online: Website | Twitter | Facebook | Linkedin | Blog Check out our Digital Accessibility Webinars! -----Original Message----- From: Patrick H. Lauke [mailto:redux@splintered.co.uk] Sent: Thursday, April 21, 2016 5:41 PM To: White, Jason J; w3c-wai-gl@w3.org Subject: Re: Do icons fall under - 1.3.3 question for shapes/icons alone that are used everywhere now but were not back in 2008 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 Monday, 25 April 2016 14:41:14 UTC