IssueTracker

Jetpack Compose version: 1.5.4

Jetpack Compose component(s) used: Material3 TextField and BasicTextField

Android Studio Build: #AI-231.9392.1.2311.11330709

Kotlin version: 1.8.10

Steps to Reproduce or Code Sample to Reproduce:

1. Visit https://github.com/Almost-Senseless-Tech/Voskle-Live-Transcribe/blob/main/app/src/main/java/tech/almost_senseless/voskle/ui/customComposables/Textarea.kt to check out the source code.
2. Pull the repo, build it, and run it on a device or emulator.
3. Active TalkBack.
4. When you navigate to the transcript text field, TalkBack will say nothing. It will speak the transcript label one swipe later, but it doesn't recognize this is a text field label, nor that the text field is... well, a text field. Additionally, the cursor remains invisible on text fields and I cannot input anything into the text field using the braille display keys, even when keyboard input is enabled; I can input using an external keyboard however.

All sources I have seen treat text fields as if they were self-explanatory and didn't pose any accessibility implications. In my experience, that's not true: Many Android apps contain inaccessible text fields which do not report the cursor position correctly and sometimes don't report that they are text fields.

I'm trying to track down the root cause of this - whether it got to do with OneUI by Samsung, their distributed TalkBack version, TalkBack itself, or JetPack Compose.