Radio buttons are graphical user interface elements that allow user to choose only one option from a predefined set of mutually exclusive options.
<nord-radio label="Option 1" name="test" value="1"></nord-radio>
<nord-radio label="Option 2" name="test" value="2"></nord-radio>
Controls whether the checkbox is checked or not.
Label for the input.
Optional hint text to be displayed with the input. Alternatively use the hint slot.
Visually hide the label, but still show it to assistive technologies like screen readers.
Placeholder text to display within the input.
Optional error to be shown with the input. Alternatively use the error slot.
Determines whether the input is required or not. An input marked as required will be announced as such to users of assistive technology. When using this property you need to also set “novalidate” attribute on a form element to prevent browser from displaying its own validation errors.
Visually hide the required indicator, but still show required attribute to assistive technologies like screen readers.
Makes the component disabled. This prevents users from being able to interact with the component, and conveys its inactive state to assistive technologies.
The name of the form component.
The value of the form component.
Gets the form, if any, associated with the form element.
Fired as the user types into the input.
Fired whenever the input's value is changed via user interaction.
|Use when a label requires more than plain text.|
|Optional slot that holds hint text for the input.|
|Optional slot that holds error text for the input.|
Programmatically move focus to the component.
Programmatically remove focus from the component.
Programmatically simulates a click on the component.
This section includes guidelines for designers and developers about the usage of this component in different contexts.
- Use a radio component when users can only select one option from a list.
- Favour radios over a select component when there are a small number of options. This reduces the number of clicks a user has to make, increasing efficiency.
- Radio buttons are grouped by their
nameattribute. Therefore, it is crucial that the same
nameis used for a group of radios.
- Give each radio within a group a unique
- Radios must be used in combination with a fieldset component.
- In most cases, a stack component should be used to layout a group of radio buttons.
- Don’t place interactive content (buttons, links etc) inside the label.
- Don’t use when a user can select more than one option. In this case, use a checkbox instead.
- Don’t use for “accepting terms of service” and similar functionality. Use a checkbox instead.
- When you have more than 10 options to choose from. Consider using a select instead.
Content guidelines #
Radio button labels should be clear, accurate and predictable. It should be possible for the user to understand what they are enabling or disabling:
When writing radio button labels, always write them in sentence case, not title case. The first word should be capitalized and the rest lowercase (unless a proper noun):
Avoid ending in punctuation if it’s a single sentence, word, or a fragment:
Do not use commas or semicolons at the end of each line
Additional considerations #
- Hint text can be used to offer further information or explanation for an option.
- Once a radio has been selected, users cannot return to having no radios selected without refreshing their browser window. Therefore, you should include "None of the above" or "I do not know" if they are valid options.
- In most cases, radio buttons should be stacked vertically. However, radio buttons can be stacked horizontally when there are only two options with short labels. An example might be a yes/no question.
If you experience any issues while using Nord Web Components, please head over to the Support page for more guidelines and ways to contact us.