WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: does talkback should announce a UI control as a button


From: Birkir R. Gunnarsson
Date: Jun 23, 2020 3:04PM

If it's a native Android button it will be announced as a button.
If it is a custom element that acts like a button, yes, it needs to be
announced as a button (all interactive elements should have the
appropriate role, that is a WCAG 4.1.2 requirement that applies just
as much on mobile apps as it does to web).
I have a code snippet that assigns a button role to a custom Android
component, but I have to dig it up.

On 6/23/20, Laura Fathauer < <EMAIL REMOVED> > wrote:
> I don't know about the programming aspect of it; but yes, TalkBack
> should still be able to announce to a user what the role of an element
> is. Otherwise the user either won't know that the element is
> interactive, or if, it it has an incorrect role, they won't know the
> proper interaction.
> Laura
> On Tue, Jun 23, 2020 at 7:16 AM konstantin galiakhmetov
> < <EMAIL REMOVED> > wrote:
>> Hello all.
>> i can not understand how talkback should announce custom controls.?
>> For example when i am testing web page i am sure that a custom button
>> implemented using <div> must have the role attribute and must be
>> announced as a button but when i am testing a native android application
>> i am doubting. If We have a custom button that is inherited a simple
>> view talkback does announce this control as a button and i do not know
>> it is bug or no.
>> sincerely Konstantin.
>> >> >> >> > > > > >

Work hard. Have fun. Make history.