I'm currently exploring rendering markdown-style links using ClickableText/AnnotatedStrings, similar to how JetChat works here: https://github.com/android/compose-samples/blob/ee198110d8a7575da281de9bd0f84e91970468ca/Jetchat/app/src/main/java/com/example/compose/jetchat/conversation/Conversation.kt#L481

I'm running into issues with matching the accessibility experience of the old View system. In the old system, URLSpans automatically provided a great accessibility UX:

When reading out any link, there would be a small ding sound to help indicate where the link is.
TalkBack tells the user that this text has links in it.
Upon opening the TalkBack context menu, there would be a "Links" submenu where the user can scroll through all of the links contained within the text.

This doesn't seem to be possible to replicate in Compose. All I can find in the semantics API is "custom actions", which is a similar but worse experience (no ding sound, no specific "links" submenu, no hint to the user that there's links to be clicked, etc).

I think this inconsistency will be confusing for accessibility users. Can we get a new API to help replicate the functionality of the View system? For example, could we add an annotation to indicate to TalkBack where the links are?

Thanks!