Video examples
iOS Voiceover
Android Talkback
MacOS Voiceover Safari
Code examples
Use semantic HTML
- This semantic HTML contains all accessibility features by default.
- It uses CSS pseudo attributes to create the radio indicator, no Javascript.
Fully disabled radio inputs
Disabled and focusable radio inputs
It’s possible to use aria-disabled="true"
so screen reader users can focus the radio button with the arrow keys. Use preventDefault()
to prevent the checkbox from being checked.
When specific radio inputs are conditionally enabled/disabled by other controls in the page this method can make ensure all radio input options are discoverable.
Required radio inputs
Ensuring all screenreaders indicate radio inputs as being required requires some aria and reinforcement.
- Use
aria-required="true"
to indicate the group is required - Use
aria-invalid="true/false"
to indicate an error state - Add
role="radiogroup"
to the<fieldset>
to make thearia-required
attribute valid - Add “Required” as text to the
<legend>
to ensure compliance across all platforms
Radio button cards
-
Delta (prounounced: dell-tah) is the fourth letter of the NATO alphabet.
-
Echo (prounounced: eck-oh) is the fifth letter of the NATO alphabet.
When you can’t use semantic HTML
This custom button requires extra scripting work for roving tabindex and event listeners.
Specialty use cases
Radio mixed with interactive elements
Avoid placing interactive elements between radio buttons.
- Radio button focus order is not what you think it is.
- When nothing is selected, tab order moves through as expected.
- However, as soon as a radio button is selected, the selected radio input receives focus first from the group.
Checkbox radio hack
- This hack must be used very carefully on a case by case basis.
- With great power comes great responsibility.
Developer notes
Name
label
text must describe the radio input.- Use
aria-describedby="hint-id"
for hints or additional descriptions aria-label="Radio input purpose"
can also be used (as a last resort)
Role
- By default, semantic HTML radio inputs identify as radio button
- Use
role="radio"
for custom elements
Group
- Semantic HTML
<fieldset>
must wrap the radio group<legend>
must describe the group’s purpose- Each
<label>
must includefor="input-id"
to be associated with its input
- Custom elements
- Use
role="radiogroup"
to take the palace of fieldset - Use
aria-labelledby="label-id"
to associate an element as a label aria-label="Group purpose"
can also be used if there’s no label with an ID
- Use
State
- Semantic HTML
checked
(will be read as “selected” by screen reader)- Use the
disabled
state for inactive buttons
- Custom element
- Use
aria-checked="true/false"
to express state - Use
aria-disabled="true"
to declare inactive elements
- Use
Focus
- Focus must be visible
- Custom elements will require keyboard event listeners and roving tabindex
- DO NOT put interactive elements inbetween radio inputs.
- Performs its purpose across platforms, devices and viewports