It doesn't work because the test tag is on a child component and the content description semantics I want to apply is on the parent component.

The issue was when we wanted to use clearSemantics to redefine the content description of several child components that contain clickable elements. The clickable item has a test tag, it has bee, removed by clearSemantics.

Currently our accessibility content description are managed by the backend driven labels to ensure consistency across platforms and localized. So it's not easily to reuse them for testing.

It would be interesting to isolate test tag from semantics or at least having a way to keep test tag when using clearAndSetSemantics method. Is there a plan to improve this? Thanks (2/2)

@anomiss.bsky.social Hello,
I have a question about accessibility in compose. Why test tag are link with the semantics ? Using test tags for automated tests and accessibility in the same time it's not easy especially with clearAndSetSemantics method. (1/2)

C'est le dessin de deux huitre, la première ouverte avec des fleurs bleues à l'intérieur pour recréer des motifs de céramique et la deuxième fermée derrière

Rendre une chose moche moins moche 😬
#inkdrawing

I will look at this API, thanks for your help :)

Is there a good way to handle testTag and accessibility ? If not, in future versions of compose will we have more flexibility to manage this? Thanks :)

@riggaroo.dev Hello,
I have a question about accessibility in compose. We use testTag for ui automation testing and recently we had to add semantics for accessibility with clearAndSetSemantics method. As the testTag is handled by the same object, it erases it if there is testTag in subcomponent.