Update the guidance on when to use the checkboxes component #4059
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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:Built without sensitive environment variables
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.