Update the guidance on when to use the checkboxes component #4059
Conversation
The guidance currently says you can use the component when you need to help users toggle a single option on or off. For these cases, it would be better to use 2 radios with yes/no or on/off because it makes users deliberately choose the option they want. Otherwise, there's the risk that users miss the single checkbox on the page and end up not selecting something they might have had selected if the page was using radio buttons.
✅ You can preview this change here:
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@CharlotteDowns @Ciandelle @hazalarpalikli @mia-allers-gds I think this change needs more of a design review than a tech one. Would any of you be able to have a look, please? |
|
OFFICIAL-SENSITIVE
Good afternoon,
I was wondering if someone has been able to pick this up or if you know when someone will be able to do so?
Many thanks,
Pablo
Pablo Charro de la Fuente (He/him)
Lead Service Designer
Elections Digital Team
Ministry of Housing, Communities and Local Government (MHCLG)
Email: ***@***.******@***.***>
OFFICIAL-SENSITIVE
From: Romaric Pascal ***@***.***>
Sent: Monday, September 9, 2024 3:53 PM
To: alphagov/govuk-design-system ***@***.***>
Cc: Pablo Charro de la Fuente ***@***.***>; Author ***@***.***>
Subject: Re: [alphagov/govuk-design-system] Update the guidance on when to use the checkboxes component (PR #4059)
You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
@CharlotteDowns<https://github.com/CharlotteDowns> @Ciandelle<https://github.com/Ciandelle> @hazalarpalikli<https://github.com/hazalarpalikli> @mia-allers-gds<https://github.com/mia-allers-gds> I think this change needs more of a design review than a tech one. Would any of you be able to have a look, please?
-
Reply to this email directly, view it on GitHub<#4059 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKVDHUUTLA5ZMHZRHIE45V3ZVWY27AVCNFSM6AAAAABM2ITQYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZYGM2DGMRRHE>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
|
@romaricpascal @Pablo-MHCLG I think this update makes sense from a usability and a guidance perspective. I'm wondering if we could add another line to the proposed guidance explaining why a radio button is better than a single checkbox? The explanation provided in this PR makes sense to me and would give the user some helpful context |
|
@Pablo-MHCLG Just checking if you've seen @mia-allers-gds's comment above? If you don't have capacity to update this pull request with the suggestion, we can try to do this for you. |
Pulling the change as requested by Owen and Mia in alphagov#4059
|
@owenatgov I'm not sure how to update the pull request, I'm not very familiar with Github, I would appreciate if you could update it for me, thank you! |
…heckboxes component
There was a problem hiding this comment.
@Pablo-MHCLG I've addressed @mia-allers-gds's comment above. I'm now happy with this!
This just needs a second approval then it can roll on in.
|
I wonder if there is a little nuance to this? Accepting terms and conditions is effectively a binary on/off choice, but using a checkbox for that is pretty standard, likewise for "remember me" functionality on a login screen, or opting in or out of marketing materials. Is there a risk of making people think they need to use radio buttons for those? Should they be using radio buttons for those? |
The guidance currently says you can use the component when you need to help users toggle a single option on or off. For these cases, it would be better to use 2 radios with yes/no or on/off because it makes users deliberately choose the option they want. Otherwise, there's the risk that users miss the single checkbox on the page and end up not selecting something they might have had selected if the page was using radio buttons.