E-mail List Archives
Re: does talkback should announce a UI control as a button
From: joe
Date: Jun 23, 2020 4:18PM
- Next message: Jonathan Avila: "Re: does talkback should announce a UI control as a button"
- Previous message: Brandon Keith Biggs: "Re: ARIA grid versus HTML table"
- Next message in Thread: Jonathan Avila: "Re: does talkback should announce a UI control as a button"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: does talkback should announce a UI control as a button"
- View all messages in this Thread
For custom elements to provide a custom role you must use
AccessibilityDelegateCompat
(https://medium.com/android-microsoft/android-accessibility-resolving-common
-talkback-issues-3c45076bcdf6#d51f), but realize doing so you are taking
over providing accessibility information for that element if something for
that element is updated.
Better to user native elements for their specified purpose, when possible.
Android does need better support for roles and states in general IMO.
Also, TalkBack users can turn off roles if they really want to:
http://www.accessibility.io/images/Android_TalkBack_Verbosity_Element_Type.p
ng
Thankx,
Joe Humbert
Accessibility Champion
Android & iOS Accessibility Novice
- Next message: Jonathan Avila: "Re: does talkback should announce a UI control as a button"
- Previous message: Brandon Keith Biggs: "Re: ARIA grid versus HTML table"
- Next message in Thread: Jonathan Avila: "Re: does talkback should announce a UI control as a button"
- Previous message in Thread: Birkir R. Gunnarsson: "Re: does talkback should announce a UI control as a button"
- View all messages in this Thread