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: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Thu, 9 Apr 2015 18:43:14 +0000
To: Jim <jhomme1028@gmail.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BY2PR03MB272F538906A4BA1E76F2D7D9BFB0@BY2PR03MB272.namprd03.prod.outlook.com>
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.  Regarding native apps, when screen readers are activated both platforms change how interactions work and place additional items into the swipe/focus order.  Essentially under iOS if an element has isAccessibilityElement set to YES it is focusable with swiping.  On android set the element to be focusable (e.g. android:focusable) to make it swipable or accessible with the keyboard.


Jonathan Avila
Chief Accessibility Officer

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

-----Original Message-----
From: Jim [mailto:jhomme1028@gmail.com] 
Sent: Thursday, April 09, 2015 2:30 PM
To: w3c-wai-ig@w3.org
Subject: Understanding How Focus Behavior Works For VoiceOver On IOS and TalkBack On Android

I'm trying to advise some developers how to sensibly help mobile screen readers land in user-friendly places when screens come up.
Before I have specific questions, I was attempting to wade through the draft accessibility API document, and because I am only a dangerous coder, and like things in non-technical language, at least to start with, can anyone point me to somewhere that I can read to understand this so that I can go from a high level and then drill down to technical things?



If building your own web site is holding you back, I can help.
Received on Thursday, 9 April 2015 18:43:45 UTC

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