RE: Questions: Android native app testing

Sorry, catching up on emails. From Android version 9 from memory, heading type (role) is now supported. The voice assist Samsung screen reader does not support this new type, talkback does.






Sean Murphy | Accessibility expert/lead
Digital Accessibility manager
Telstra Digital Channels | Digital Systems
Mobile: 0405 129 739 | Desk: (02) 9866-7917

www.telstra.com

This email may contain confidential information.
If I've sent it to you by accident, please delete it immediately



-----Original Message-----
From: Patrick H. Lauke <[email protected]> 
Sent: Tuesday, 11 February 2020 7:13 PM
To: [email protected]
Subject: Re: Questions: Android native app testing

[External Email] This email was sent from outside the organisation – be cautious, particularly with links and attachments.

On 10/02/2020 19:39, Sailesh Panchang wrote:

> 2. Sometimes  that an element is a heading or a button is conveyed via 
> android:contentDescription. As a result the item is not discoverable / 
> navigable using a selection via TalkBack's local context setting. This 
> in effect impairs the ability to use a documented accessibility 
> feature so is an accessibility failure directly  transgressing a 
> requirement for software accessibility IMO. However, "Don't include 
> the type of UI element in the content description" is merely noted as 
> a best practice at 
> http://developer.android.com/guide/topics/ui/accessibility/apps.html.

For headings at least, I believe this was an old workaround for the time when it was simply not possible to actually convey that something was a heading any other way in native Android, and accessibility-minded devs adopted this as the least bad thing.

P
--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke