- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Mon, 18 Jul 2016 10:53:46 -0400
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Cc: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Jonathan- you and I are ad idem! Sailesh On 7/18/16, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote: >> Isn't this the effect of VO intercepting handwriting and gesture features, >> rather than a problem with the actual content itself? Once VO is on, >> content/apps on webpages don't get the raw touch information anymore, it's >> all mediated via VO. > > I think he's talking about the rotor feature where you can set the rotor to > handwritten input and draw letters on the screen for input rather than an > actual handwriting field. > > 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: Monday, July 18, 2016 10:15 AM > To: w3c-wai-gl@w3.org > Subject: Re: New SC: Avoid disrupting working accessibility features > > On 18/07/2016 15:09, Sailesh Panchang wrote: >> Sometimes I have run into an issue that prevents use of handwriting >> feature on an iPhone/iPad when VO is on on a Web page and sometimes >> in an app. The new SC will cover this. > > Isn't this the effect of VO intercepting handwriting and gesture features, > rather than a problem with the actual content itself? Once VO is on, > content/apps on webpages don't get the raw touch information anymore, it's > all mediated via VO. > > 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, 18 July 2016 14:54:17 UTC