-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smaller checkboxes and radio buttons #162
Comments
@frankieroberto Same contribution. But we decided to create a fresh issue and archive the old one. |
@owenm6 I've been using the code from your proposal to build a miller columns prototype. I consider this being valuable to make the most of the space while ensuring the checkboxes are accessible especially when needed as part of another component (be that a table, a dropdown list or in our case a miller columns component). |
Working group review sessionThis proposal was reviewed by the Design System working group on 25 Oct 2018. The group agreed that the proposal can be taken forward as a contribution to the GOV.UK Design System because:
Some members were unsure whether the proposal met the ‘unique’ criteria because it’s a variation on an existing component. After a discussion the group agreed that the criteria should be iterated to clarify that variations that meet specific common use cases are allowed. The group also made the following comments and recommendations for future work. Design
Research
Guidance
|
You can see these used in the GOV.UK Publishing 'options select' component: https://finder-frontend.herokuapp.com/component-guide/option-select This is used in the https://github.com/alphagov/finder-frontend application. An example of it used in a page: https://www.gov.uk/employment-tribunal-decisions Update: They have now updated to use smaller checkboxes... |
Another example that is similar to @alex-ju in that it uses a full clickable row to increase the click area: https://home-office-digital-patterns.herokuapp.com/components/table-multiselect |
I'd love to see these in use - we have a column of filters in our list of things, and smaller checkboxes would give us much needed screen real-estate. |
Working group review sessionThis proposal was reviewed by the Design System working group on 28 February 2019. The working group is a multidisciplinary panel of 11 representatives from HMCTS, GDS, HMRC, DWP, Environment Agency and Home Office. The group agreed that small radios and checkboxes can be published in the GOV.UK Design System. The working group also made the following recommendations. Guidance
Examples
|
Content edits to address [working group review feedback](alphagov/govuk-design-system-backlog#162 (comment))
Content edits following [working group review feedback](alphagov/govuk-design-system-backlog#162 (comment)).
Content edits to address [working group review feedback](alphagov/govuk-design-system-backlog#162 (comment))
Content edits following [working group review feedback](alphagov/govuk-design-system-backlog#162 (comment)).
What
This is a proposed addition to the existing checkboxes and radios components.
The proposal is to add smaller versions of these form controls, and guidance on when and when not to use them.
Why
Smaller checkboxes and radios allow more information to be included on a screen. This can be useful in services designed for regular use, where users need to work efficiently, such as case working and administration systems.
They can also be used to create visual hierarchy in more information rich user interfaces such as these.
These components are already being used in government services. However, the implementation and design is currently inconsistent, and there are instances of these components being misused.
Adding these components to the design system would allow us to standardise them and give guidance on their appropriate use.
Examples
Examples of services using these components include:
Common use cases for these components include:
Selectable table rows
Search filters
Anything else
Smaller radios and checkboxes will be harder for some people to use, because the hit area is smaller. They should be implemented in a way which minimises this issue.
These components should be carefully tested on smaller screen devices to check that they are still usable.
There’s a risk that smaller radios and checkboxes might be used as a way to fit more things on the screen, when another approach might be more appropriate. The guidance should be carefully written to mitigate against this.
Related links
The text was updated successfully, but these errors were encountered: