RE: Clarifying new Technique: Providing touch access for custom controls

> I'm not aware of any specific events that would be fired / can be interecepted by scripts here. My gut feeling is that there is no (or at least no consistent) way of achieving this (other than perhaps having a real slider visually hidden, but taking VoiceOver/TalkBack focus, and having the faked/prettified slide update based on this hidden slider).

This is my understanding as well.

Jonathan

-- 
Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
jon.avila@ssbbartgroup.com

703-637-8957 (o) 
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter


-----Original Message-----
From: Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Sent: Friday, December 04, 2015 10:22 AM
To: public-mobile-a11y-tf@w3.org
Subject: Re: Clarifying new Technique: Providing touch access for custom controls

On 04/12/2015 15:03, Detlev Fischer wrote:
> Option 1.B
> The focus of the technique is on implementing standard native screenreader gestures for  custom controls.
> E.g. with VO on, the value of a native slider (range) can be set via the iOS rotor. Not sure how well that is natively supported elsewhere. It *should* work the same way for custom controls properly marked up as range, but doesn't (at least doesn't on http://files.paciellogroup.com/blogmisc/samples/aria/slider/ ).
> So the Technique would describe something that ought to work and may work soon (given improvements of AT / UA).

I'm not aware of any specific events that would be fired / can be interecepted by scripts here. My gut feeling is that there is no (or at least no consistent) way of achieving this (other than perhaps having a real slider visually hidden, but taking VoiceOver/TalkBack focus, and having the faked/prettified slide update based on this hidden slider).

> Option 1.C
> Implementing gestures (such as multi-finger swipe or drag) known from native apps for non-discrete settings of value.
> There is the issue of potential gesture conflicts with AT so I am not sure whether this shold ever be recommendad in a Technique. Even if a three finger drag could be scripted and somehow communicated as the means to increase/decrese the value, it may already be taken by some other AT (e.g. moving the enlarged section wehen Zoom is activated in iOS) so it may not work.

To my knowledge, there is no consistent way to allow custom sliders to be made accessible to screenreader users without relying on pass-through gestures. The fact that a widget relies on this cannot be programmatically flagged/announced by AT to my knowledge, either - so would rely on explicit additional instructions given to AT users, making it rather clunky.

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, 7 December 2015 02:40:49 UTC