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/patrickhlaukehttp://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke