:android-wave: Touchables A11y
After disabling Tal...
# compose-androidj
Jonas
12/14/2023, 9:27 AM👋 Touchables A11y
After disabling TalkBack it’s necessary to select a Button/TextField/BottomNavigation item twice each time.
Anyone an idea why this is happening and if there is a workaround?
https://issuetracker.google.com/issues/316195053
Jonas
12/14/2023, 9:28 AMissue-demo.mp4,sample-project.zip
t
Timo Drick
12/14/2023, 9:51 AMFor me it looks like you are still in talkback mode. So i assume you meant "After enabling TalkBack ...."
And this is normal behavior of the android system. So you should not change this.
j
Jonas
12/14/2023, 9:53 AMNo, I mean after disabling Talkback.
You can see that it is disabled as there is no blue border indicator anymore.
Jonas
12/14/2023, 9:55 AM(In second 5 it gets disabled).
There are detailed steps how to reproduce this in the issue above.
Jonas
12/14/2023, 9:56 AMIt is important that you select a BottomNavigationItem after turning on TalkBack. The bug occurs after you turn off TalkBack afterwards. You need to press twice on a BottomNavigationItem before it is selected.
1. Turn on TalkBack
2. Select any Item in BottomNavigationBar
3. Turn off TalkBack
4. Select any Item in BottomNavigationBar
5. See Issue (see attached video)
t
Timo Drick
12/14/2023, 10:06 AMAh ok sorry. Did not watch the full video. I tryed it in one of my apps and i do not have this issue. At least not on my device.
Timo Drick
12/14/2023, 10:18 AMOk no i do have this issue. When i use a shortcut for talkback
j
Jonas
12/14/2023, 10:25 AMAh, thats an interesting inside gratitude thank you
t
Timo Drick
12/14/2023, 10:25 AMYes it looks like an compose error. In youtube app it does not happen
j
Jonas
12/14/2023, 10:37 AMOk no i do have this issue. When i use a shortcut for talkbackWhat was your way of disabling TalkBack that does not produce the issue? We tried: • Floating shortcut • Shortcut in navigation bar • Volume keys • Through settings (turning on and off with the same way each) In each scenario the bug occurs on our side.
t
Timo Drick
12/14/2023, 10:41 AMI did a bit more testing and i can not reliable reproduce the error. Sometimes it happens sometimes not.
Timo Drick
12/14/2023, 10:46 AMBut it is there. Btw. it also happens for normal buttons not just for the navigation bar. And in my tests it hits the last tapped button. And only after a second tap it hits the correct button
j
Jonas
12/14/2023, 12:01 PMThx for testing.
Thats also interesting. Means this is a broader issue. Do you mind adding this information to the issue?
t
Timo Drick
12/14/2023, 12:18 PMHmm interesting it looks like that not all interactions do have the problem. Looks like a switch is working fine. But i see this problem for clickable modifier. But also not for all.
Timo Drick
12/14/2023, 12:22 PMUnfortunately the bug is not really visible in the screen recording. I turned show taps in devsettings on but it is not in the recording.
j
Jonas
12/14/2023, 12:32 PMThx for adding the addition information to the ticket.
You are right, it’s quite hard to follow the recordings without the tapindicator.
d
dorche
12/15/2023, 12:55 AMI am getting the same behaviour on my Material3 textfields - have to tap twice to focus the field after disabling talkback
j
Jonas
12/15/2023, 5:27 AMThx for the info @dorche.
Can you add it to the issue?
Unfortunately I can’t update the title to make it more broad.