WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Missing control type of components in mobile

for

From: Jonathan Avila
Date: Aug 3, 2017 6:26AM

> Being strict here, if this is a shortcoming in Talkback, rather than anything incorrect/missing in markup, then I'd say it's not a violation of 4.1.2, and the fault lies with Talkback.

This is a product of how Android works. The challenge is if you are testing without having access to the code or some sort of tool that could inspect the accessibility tree then you don't know if a button was constructed using a button or with some other element that is touchable but happens to work correctly with assistive technology. While there are accessibility services based testing tools on Android like Google's Accessibility Scanner -- you generally don't know the actual roles like you would have access to in the DOM or through inspection of the accessibility API on other platforms like Windows and Mac.

Jonathan

Jonathan Avila
Chief Accessibility Officer
Level Access, inc. (formerly SSB BART Group, inc.)
<EMAIL REMOVED>
703.637.8957 (Office)
Visit us online: Website | Twitter | Facebook | LinkedIn | Blog
Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Patrick H. Lauke
Sent: Thursday, August 03, 2017 5:25 AM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] Missing control type of components in mobile

On 03/08/2017 07:49, surbhi Mudgal wrote:
> Hi All,
>
> Hope all doing good.
>
> In mobile while testing an application on android with talkback observe
> that control type of the elements are not announced on focusing but
> talkback gives the instruction "double tap to activate".
>
> It's a violation under WCAG4.1.2 if the role is not exposed to screen
> readers but what could be the impact if control type is missing
> announcing the instructions like "double tap to activate"? Hearing to
> instruction user for sure activates items and I would like to know
> which users have more impact due to this behavior?

Being strict here, if this is a shortcoming in Talkback, rather than anything incorrect/missing in markup, then I'd say it's not a violation of 4.1.2, and the fault lies with Talkback.

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