RadioButton, Checkbox, & Switch don't meet 48dp tap target requirements for accessibility [171509422]

Fixed

Bug

Status Update

No update yet.

Description

al...@gmail.com

created issue #1

Oct 23, 2020 05:19PM

It seems like these are all designed to be used as standalone components (given that all have onClick arguments and Switch can be swiped for example). But all of them have tap targets that are less than 48dp (given that their physical size is smaller than that).

Should their size be increased to account for this?

Or maybe there an equivalent to TouchDelegate that could be used to expand the tap target size?

Otherwise it seems odd that these components have onClick arguments, since I think that may discourage people from implementing accessible tap targets properly.

Comments

cl...@google.com <cl...@google.com> Oct 23, 2020 05:20PM

Reassigned to ma...@google.com.

ma...@google.com <ma...@google.com> #2Oct 26, 2020 11:05AM

May I ask why P3? This is blocking for me to go to prod, I'd really like some inputs about what is going on so I can either fix or build a repro to have this fixed.

ae...@google.com <ae...@google.com> #3Oct 26, 2020 09:59PM

Unfortunately I am unable to reproduce it as well. Maybe there is a chance you can share your code with me? You can send it to my email as you did previously already.
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?

ma...@google.com <ma...@google.com> Aug 17, 2021 07:12PM

Reassigned to mo...@google.com.

ap...@google.com <ap...@google.com> #4Aug 31, 2021 09:49PM

It happens even on screens that does not use the layoutInfo it just require many up / down flings.

LazyColumn(state = rememberLazyListState())

The only thing all screen have in common in that they have multiple item {} item{} block :(

Just in case the app is in open beta at https://play.google.com/store/apps/details?id=app.symfonik.music.player but don't think you can see much except repro.

My main question before trying to do complex repro, is how much will it be relevant with all the recent changes in alpha 8 about Lazy stuff? And side question when https://issuetracker.google.com/issues/229752147 is fixed (it touches all my screens maybe another indicator?) will there be some snapshot build with the fix so I can directly try to repro on that?

lp...@google.com <lp...@google.com> Sep 2, 2021 06:05PM

Reassigned to lp...@google.com.

ap...@google.com <ap...@google.com> #5Sep 21, 2021 04:34PM

Marked as fixed.

I can't guarantee as I don't understand the issue yet, but I assume this issue is still not fixed, changes in alpha 8 were about different things. b/229752147 is fixed already in the main branch, so any recent snapshot from androidx.dev should contain it already if you want to try