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

The html radio input

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
MUST convey an appropriate namesupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey an appropriate rolesupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the checked statesupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the unchecked statesupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey a change in the checked statesupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the position in set informationpartial (4/6)supportedsupportednonenonesupportedsupported
SHOULD provide shortcuts to jump to this rolesupportedsupportedpartial (2/4)supportedsupportedsupportedsupported

Voice Control support by expectation

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

Expectation: convey an appropriate name

Rationale: A screen reader user needs to know what to enter.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST

Examples of assistive technologies support this expectation:

  • 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 an appropriate 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 an appropriate 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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST

Examples of assistive technologies support this expectation:

  • 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 an appropriate 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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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 these expectations for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA