Order of accessibility nodes is wrong

[SebastianAigner]

1.6.10-rc01

https://github.com/Kotlin/KMP-App-Template/tree/426bead7f26ba27ba1facfbfd1d5c0f7628a437a

[elijah-semyonov]

Hm, what's the situation on Android? This is a single Element, so based on mismatch of visible text and Accessibility label I assume the data there was merged. The merging of semantics in the subtree is done in the order described here.

We either have a runtime bug that somehow causes this order to be different from order in which underlying nodes are apparently emitted in code, or it's a Google-side bug/(feature?).

A workaround for now would be to use Modifier.clearAndSetSemantics with SemanticsPropertyReceiver.text and explicitly provide the string to be visible by a11y services.

[tylerwilson]

I have a similar if not the same issue in my app: it will read starting from the second element, go to the end, and then go back and read the first element. I was using a Column, then switched to a LazyColumn, but same result.

Hope the cause can be found and fixed. Thank you.

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.