Skip to main content
Coat of arms of Barbados
Official government website

Label

Names the field it sits above. Every form control needs one.

Preview

Label with hint text

The Label component names the field it sits above, so users know what answer is expected before they start typing. Every form control (input, select, text area, checkbox, or radio) needs a visible label.

When to use this component

Use a label on every form control, without exception. Associate it with its control using for and id so clicking the label focuses the control, and so assistive technology announces the label whenever the control receives focus.

When not to use this component

Do not use placeholder text in place of a label. Placeholder text disappears as soon as the user starts typing, offers no persistent reminder of what is being asked, and is easy to miss , particularly for users of screen magnification or those who are easily distracted.

Writing label text

Write labels as short noun phrases, such as "Email address", rather than questions or instructions. Keep the label focused on naming the field. Put any extra detail, such as an expected format or example, in hint text instead.

Pairing with hint text

Use hint text (.govbb-hint) beneath the label to explain a format or give an example, such as "It is on your national ID card". Link the hint to its control with aria-describedby so it is announced alongside the label.

Label without hint text

Grouping controls

Use only one label per control. To name a group of related controls, such as a set of checkboxes or radio buttons, use a <fieldset> with a <legend> instead of a label. This frames the question for the whole group rather than a single field.