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

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

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

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

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

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

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.

deleted