|
| 1 | +--- |
| 2 | +title: Labels and questions in forms |
| 3 | +category: Content work |
| 4 | +description: Good labels make it easier for users to understand what to answer. |
| 5 | +author: Digdir, KS, Nav ++ |
| 6 | +search_terms: questions, labels, wording |
| 7 | +date: 2026-05-20 |
| 8 | +order: 10 |
| 9 | +published: true |
| 10 | +--- |
| 11 | + |
| 12 | +A label is the text that tells users what to answer for each field in a form. You can use a description to help users understand difficult terms, or explain why they need to answer. Some call labels question text and descriptions help text. |
| 13 | + |
| 14 | +It is especially important to think about how you ask questions in public services, because users are often afraid of answering incorrectly. |
| 15 | + |
| 16 | +<Story story="WithRowsEn" /> |
| 17 | + |
| 18 | +Only ask for information you need. |
| 19 | + |
| 20 | +Consider |
| 21 | +- whether you can reuse information you already have about the user |
| 22 | +- why you need the information |
| 23 | +- what you will do with the information |
| 24 | + |
| 25 | +## Think of the text as a conversation |
| 26 | +When we address users directly with “you” and “I”, the content feels less technical and more like a conversation. It also makes it easier for users to understand what to answer. |
| 27 | + |
| 28 | +Check that the answer options can be read as a logical response to the label. Consider including answer options users can choose if they do not know what to answer, for example “I am not sure” or “I do not know”. |
| 29 | + |
| 30 | +<div className="dodont-row"> |
| 31 | + <DoDont story="DoLabelEn"> |
| 32 | + Use **you** when you |
| 33 | + - write labels and questions |
| 34 | + - give information to the user |
| 35 | + |
| 36 | + Use **I** when |
| 37 | + - the user answers through checkboxes, radio buttons or dropdowns |
| 38 | + - the user gives examples of answers |
| 39 | + - the user consents to something |
| 40 | + </DoDont> |
| 41 | +</div> |
| 42 | + |
| 43 | +## Write short and precise labels |
| 44 | +Users prefer short texts, especially when they are stressed, busy or reading on a small screen. |
| 45 | +Use established wording when you can to keep labels as short as possible. |
| 46 | + |
| 47 | +Choose between established wording, descriptive prompts or questions. |
| 48 | + |
| 49 | +These three ways of writing labels work best in slightly different situations. |
| 50 | +- Use established wording when users are not in doubt about what the answer is, for example National identity number and Marital status. |
| 51 | +- Use questions when the topic and answer options are less familiar to users. Questions also make the tone feel more approachable. |
| 52 | +- Prompts can help make the label shorter and more precise compared to questions. |
| 53 | + |
| 54 | +<div className="dodont-row"> |
| 55 | + <DoDont story="DoFormEn"> |
| 56 | + Use established wording and descriptive prompts when they make the label shorter and clearer. |
| 57 | + </DoDont> |
| 58 | + <DoDont story="DontFormEn"> |
| 59 | + Avoid questions when a short label or prompt is easier to understand. |
| 60 | + </DoDont> |
| 61 | +</div> |
| 62 | + |
| 63 | +Questions often lead users to answer briefly. If you need a more detailed answer, a prompt may be better, for example “Describe what you need help with during a day”. |
| 64 | + |
| 65 | +## Use closed questions when you can |
| 66 | +Closed questions are easier to answer than open questions. Users have to formulate the answer themselves when the question is open. A closed question can often be answered with Yes or No, or with obvious answer options. For example, “Which municipality do you live in?”. |
| 67 | + |
| 68 | +<div className="dodont-row"> |
| 69 | + <DoDont story="DoClosedEn"> |
| 70 | + Use closed questions when you can. |
| 71 | + </DoDont> |
| 72 | + <DoDont story="DontOpenEn"> |
| 73 | + Avoid open questions when you can. |
| 74 | + </DoDont> |
| 75 | +</div> |
| 76 | + |
| 77 | +## Avoid questions with negations |
| 78 | +Questions with negations can be difficult to understand. These are often sentences with “not” or “never”. |
| 79 | + |
| 80 | +<div className="dodont-row"> |
| 81 | + <DoDont story="DoNegationsEn"> |
| 82 | + Ask the question without negations. |
| 83 | + </DoDont> |
| 84 | + <DoDont story="DontNegationsEn"> |
| 85 | + Avoid questions with “not” and other negations. |
| 86 | + </DoDont> |
| 87 | +</div> |
| 88 | + |
| 89 | +## Give all relevant information before users answer |
| 90 | +Users should not have to try and fail, so give them all relevant information before they choose an option or fill in a field. Avoid guidance text inside the input itself, also known as placeholders. Placeholders disappear when the field is filled in, and may conflict with accessibility requirements. |
| 91 | + |
| 92 | +Sometimes descriptions, also known as help text, are useful for explaining something difficult, such as legal terms or specialist language. |
| 93 | + |
| 94 | +Only use descriptions where they are needed, to reduce cognitive load. |
| 95 | + |
| 96 | +<div className="dodont-row"> |
| 97 | + <DoDont story="DoPlaceholderEn"> |
| 98 | + Give necessary information before the user answers. |
| 99 | + </DoDont> |
| 100 | + <DoDont story="DontPlaceholderEn"> |
| 101 | + Do not use placeholder text as the only guidance. |
| 102 | + </DoDont> |
| 103 | +</div> |
| 104 | + |
| 105 | +## Build trust by explaining why we ask |
| 106 | + |
| 107 | +It can be useful to briefly explain why we ask for something, to build trust and openness. One way to do this is with an expandable description. |
| 108 | + |
| 109 | +<Story story="WithExpandableDescriptionEn" /> |
| 110 | + |
| 111 | +<Contributors |
| 112 | + headingLevel={2} |
| 113 | + authors={[ |
| 114 | + 'Dorte Drange (Digdir)', |
| 115 | + 'Marianne Røsvik (Digdir)', |
| 116 | + 'Gørild Døhl (Digdir)', |
| 117 | + 'KS', |
| 118 | + 'Skatteetaten', |
| 119 | + 'Nav', |
| 120 | + 'Helsenorge', |
| 121 | + 'Lånekassen', |
| 122 | + 'Oslo kommune' |
| 123 | + ]} |
| 124 | +/> |
0 commit comments