Bryan Herbst11/02/2020, 3:07 PM
is present). However, this is missing for some prominent components such as
, with no public API to influence that behavior. This behavior is also a bit clunky given that it relies on labeling Compose widgets as specific
classes. Is there a plan to surface something to support this? Is the TalkBack team exploring ways of decoupling TalkBack from the View APIs to better support Compose in the future?
if we want TalkBack to say “button”?
Alexandre Elias [G]11/02/2020, 11:15 PM
have the same behavior as Android Button in TalkBack by the time of Compose 1.0 release, and add whatever core public APIs are needed for third-party Buttons to have the same behavior
, we haven't been able to come up with any particular semantic trait that distinguishes one from a general
, so we will probably need to introduce a new minimalistic disambiguation system to replace classnames
Bryan Herbst11/02/2020, 11:42 PM