W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

Re: Understanding How Focus Behavior Works For VoiceOver On IOS and TalkBack On Android

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Fri, 10 Apr 2015 00:46:20 +0100
Message-ID: <55270F4C.6020406@splintered.co.uk>
To: w3c-wai-ig@w3.org
On 09/04/2015 22:31, Howard Leicester wrote:
> Great conversation!
> Thinking, though, does mean we have multiple approaches, dependent on
> platform?
> Or:
> * Is there a common approach that might work across all platforms?
> Personally believe a common approach based on WAI mobile approach.
> But appears each company is doing their own thing.It may not make a
> difference, but (if dependent on Assistive Technologies or expecting a
> common interface) not that good for many with 'special needs'?

The common approach is to explicitly manage focus (speaking purely of 
web content here, using the actual focus() method to make sure things 
are explicitly set to have focus as a result of an action, like closing 
a modal dialog).


> -----Original Message-----
> From: Patrick H. Lauke [mailto:redux@splintered.co.uk]
> Sent: 09 April 2015 19:55
> To: w3c-wai-ig@w3.org
> Subject: Re: Understanding How Focus Behavior Works For VoiceOver On IOS and
> TalkBack On Android
> On 09/04/2015 19:43, Jonathan Avila wrote:
>> Jim, it depends on whether you are talking about native apps or web apps.
> For web apps you can use the standard practices for web accessibility.
> One interesting/specific aspect of VO/iOS (may also extend to VO/OS X,
> but not tested on that platform in a while) is that if focus is lost
> (e.g. a <button> was focused, and it's then removed from the DOM/hidden
> via display:none), VO will attempt to find a focusable element that's
> closest to the position of its last known focused element...so for
> instance, if you had a modal dialog and the user focuses and activates
> the close button, and you don't explicitly manage focus by moving it
> programmatically back to a sensible place (e.g. the control that first
> triggered the modal), VO will compensate by then focusing whatever is
> near enough to the position previously occupied by the close button in
> the main page.
> Depending on the page you're testing, this can look like completely
> erratic behavior, until you realise it's VO's compensating for lost
> focus (rather than resetting focus back to start of page, as happens in
> many other ATs)
> 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, 9 April 2015 23:46:43 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC