Talkback announces non-meaningful content (e.g. "start X pixels") as user navigates markdown content

[sn-michiyo]

Bug Description

Talkback announces things like "start X pixels" as user navigates markdown content

Steps to Reproduce

Steps to reproduce the behavior:

1. Run sample Android app
2. Turn on talkback
3. use swipe navigation to listen to content

Expected Behavior

Talkback does not contain layout information (if that's what it is?) like "start 100 pixels" or "end 100 pixels" that may confuse a talkback user.

Actual Behavior

Talkback announces things like "start 100 pixels" or "end 100 pixels".

Screenshots (turn on player audio to hear talkback)

talkback_pixels.mp4

Environment

• Library Version: 3.38.1
• Platform: Android
• Device: Pixel 7 Pro
• OS Version: Android 16
• Kotlin Version: [not sure, I'm on commit bed5ff5 in the sample app]
• Kotlin Version: [not sure, I'm on commit bed5ff5 in the sample app]

Checklist

• I have searched for similar issues
• I have checked the sample application
• I have read the README
• I have checked the CHANGELOG
• I have read the MIGRATION GUIDE

[sn-michiyo]

I discovered that I can get rid of this by turning off "Speak text formatting" in the device's talkback settings > Verbosity. This is new in talkback 16.2. However, this still doesn't seem like expected behavior. With "Speak text formatting" on, I poked around a few other apps and didn't hear "start X pixels" being spoken anywhere, though admittedly it was not any kind of exhaustive testing.

[mikepenz]

Given the Speak text formatting setting. this seems like it's meant to behave this way 🤔

More than happy though to take a PR if there's something that can be improved.

[bpappin]

Just ran into this, but if its the expected behaviour we should keep it.
I think some research is in order.

Thanks Mike, for taking accessibility seriously.