UNPKG

@utrecht/components

Version:

Components for the Municipality of Utrecht based on the NL Design System architecture

github.com/nl-design-system/utrecht

87 lines (51 loc) • 3.01 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
<!-- @license CC0-1.0 --> # Form field with checkbox ## Introduction Checkboxes are usually used to provide a way for users to make a range of selections (zero, one or more). They can also be used to tell users that they agree to specific terms. ## When to use Checkboxes are used for multiple choices, not for mutually exclusive choices. Each checkbox works independently from other checkboxes in the list, therefore checking an additional box does not affect any other selections. ### Forms Can be used in forms on a full page or in modals. ### Terms and conditions Turning the checkbox input on or off can indicate whether you agree to the terms. ## Alternatives and related components Use radio buttons to display a list of options where users can only make one choice. ## Anatomy The checkbox consists of: 1. Label (optional): indicates what should be selected below. 2. Checkbox input: a checkbox input that indicates the correct status. By default it is not active. 3. Checkbox label: describes the information you can select or deselect. 4. Helper text (optional): displays more information about the checkboxes ## (Interactive) states The checkbox contains the states normal, hover, disabled, error and focus. ## Accessibility Screen readers automatically report the status of the check box. ### Labeling ### External links ### Keyboard support - Move focus to each checkbox using the tab key (or shift + tab when tabbing backwards) - Activate or deactivate checkboxes with the space key ## Content guidelines ### Checkbox labels Checkbox labels must: - Start with a capital letter - Not end in punctuation if it’s a single sentence, word, or a fragment - In case the checkbox asks to agree to the terms and conditions, use the first person ## Best practices ### Do's Checkboxes must: - Work independently of each other: selecting a checkbox may not change the selection status of another checkbox in the list. - Be positively boxed: for example “Enable notifications” instead of “Disable notifications”. - Always have a label handy when you use it to turn a setting on or off. - Use label tags as click targets. - Be arranged in a logical order, whether alphabetical, numeric, time-based or some other clear system. - Link to more information or have a subtitle for more explanation. Don't rely on tooltips to explain a checkbox. - If they are too long, run over the second line. This is preferable than truncation. - If they are too long, they will be aligned left - If they are too long, let the text flow under the checkbox so that the control and label are aligned at the top. ### Don'ts Checkboxes must: - Not cut with an omit task if the label is too long and run over 2 lines. ## References - [https://www.nngroup.com/articles/checkboxes-vs-radio-buttons/](https://www.nngroup.com/articles/checkboxes-vs-radio-buttons/) - [https://uxplanet.org/checkbox-and-toggle-in-forms-f0de6086ac41](https://uxplanet.org/checkbox-and-toggle-in-forms-f0de6086ac41)