hello 👋 in the context of our migration to Compose, we are trying to implement

accessibility

and

test tags

to the best of our knowledge and understanding. Both are based on

semantics

, but seem to fulfill different objectives. We are encountering a case where they are in conflict: to have a smoother accessibility experience, we are using

clearAndSetSemantics

on some complex components, like a collapsable header, in order to provide a global and complete

content description

, and reduce navigation steps. To note that

mergeDescendants

is not acceptable for our usecase, because the result is not understandable, hence we prefer to create by hand a global

content description

. However we would still like to access every single sub-elements from this component in our UI tests, but the

test tags

seem to be cleared because of

clearAndSetSemantics

used on the parent node. Did some of you encounter the same issue? Any workaround? Or do you think we may be doing something wrong? I will put a concrete example in 🧵

You can try defining custom semantic actions and properties for tests if you wish to clear child semantics completely.

Thanks for your suggestion, I will have a look. I thought that this was a standard usage and that would be covered by the standard API.