IssueTracker

For testing, might be related to b/207325144.

Hmm, without a revamped next-generation API, I'm not sure there's anything natural we can do to improve the behavior by default here. It might make the most sense to tell developers using ClickableText to add semantics manually adding custom actions for each clickable section.

I see the API is designed to support multiple hyperlinked spans in the same text, by passing back the character offset to the handler. It's an imperative mechanism so not well-suited to automatic accessibility behavior. I see Zach has a WIP adding an onClick(offset = 0), but that would only work when the entire text is clickable.

And the View system behavior for clickable text is documented here as "Hyperlinks within TextViews should not be independently focusable, but should be extracted into TalkBack’s Menu". I think that implies it doesn't use onClick but has one Custom Action per hyperlink, even when there is only one link.

ClickableText is deprecated in 1.7.x release. Please use a LinkAnnotation annotation of the AnnotatedString instead. The new API makes the links accessible to the Android accessibility services like Talkback, and provides a testing API.

If you can't migrate to 1.7.x and continue to use earlier version of Compose, please provide accessibility support manually. One option is to set UrlAnnotation that will expose the part of the string to the Talkback. Alternatively you could provide custom semantics actions but is not recommended for accessibility support as this provide unfamiliar user experience with the links.