Notice: This is a work in progress. Please submit feedback or suggestions.

input[type="radio"] element (html)

Screen reader support level: partial (114/120)

Voice Control support level: supported

On this page

About this feature

The html radio input

Age of results

Results across all tests for this feature range from a year ago to a year ago. Detailed dates and version information can be found in associated tests.

Caution

Failing or partial results may be out of date. The oldest result is from a year ago. Consider running the associated tests and contributing results.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey its namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey its rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the checked statesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the unchecked statesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey a change in the checked statesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the position in set informationsupportednonesupportedsupportedsupportedsupportednonenonesupportedsupported
SHOULD provide shortcuts to jump to this rolesupportedsupportedsupportedsupportedpartialsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
MUST convey its namesupportedsupportedsupportedsupportedsupported
MUST convey its rolesupportedsupportednot applicablesupportedsupported

Expectation: convey its name

Rationale:

A screen reader user needs to know what to enter.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST

Notes:

For form inputs - commands to read line by line (down and up arrows in most windows screen readers) will not always result in the name being explicitly conveyed when the virtual focus is moved to an input where the label is visually displayed and programmatically associated with the input. This is acceptable because the name is implied by the fact that it should be naturally found in the reading order. Some screen readers choose to not convey the name in these cases, likely in an effort to reduce verbosity.

Examples:

  • A screen reader will announce the name (label).
  • Voice control software will let the user say something like "click <name>" to activate the control.
Voice Control support for 'MUST convey its name'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
aria-required attribute on each HTML radio button in a fieldsetsupportedsupportedsupportedsupportedsupported
The html required attribute on each HTML radio button in a fieldsetsupportedsupportedsupportedsupportedsupported

Expectation: convey its role

Rationale:

A screen reader user needs to know how they can interact with the element. Voice control software might use the role to help users activate controls that do not have a visible name.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST

Examples:

  • A screen reader might be announce the role as "radio"
  • Voice control software will let the user say something like "click radio" to focus a the input or flag the role with a number.
Voice Control support for 'MUST convey its role'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
aria-required attribute on each HTML radio button in a fieldsetsupportedsupportednot applicablesupportedsupported
The html required attribute on each HTML radio button in a fieldsetsupportedsupportednot applicablesupportedsupported

Expectation: convey the checked state

Rationale:

A screen reader user needs to know if the checkbox is checked

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might announce "checked"

Expectation: convey the unchecked state

Rationale:

A screen reader user needs to know if the checkbox is checked

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might announce "unchecked" or imply that the element is not checked by not announcing the checked state at all.

Expectation: convey a change in the checked state

Rationale:

A screen reader user needs to know if the checkbox is checked

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might announce "checked" or "not checked"
  • A screen reader might announce the entire control again with the new state

Expectation: convey the position in set information

Rationale:

A user needs to where the position is in the list

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might something like "1 of 6".
Screen Reader support for 'MUST convey the position in set information'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
aria-required attribute on each HTML radio button in a fieldsetsupportednonesupportedsupportedsupportedsupportednonenonesupportedsupported
The html required attribute on each HTML radio button in a fieldsetsupportednonesupportedsupportedsupportedsupportednonenonesupportedsupported

Expectation: provide shortcuts to jump to this role

Rationale:

Screen reader users might want to quickly navigate to elements of this type.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA