Important: This website does not attempt to establish a standard for how assistive technologies must behave. Read the FAQ for more information. Additionally, this is a work in progress. Please submit feedback or suggestions.

radiogroup role (aria)

Screen Reader support level: partial (23/33)

On this page

About this feature

A group of radio buttons.

Age of results

Results across all tests for this feature range from 3 years ago to 5 years 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 5 years ago. Consider running the associated tests and contributing results.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
MUST convey its rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonenonesupported
MUST convey the group name if it has a group namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonenonesupported
MUST convey the boundaries of the groupsupportedsupportedsupportedsupportedpartialpartialpartialpartialnonenonesupported

Expectation: convey its role

Rationale:

A screen reader user needs to be aware that elements are within a group

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • The role name is announced when entering the group.
  • If focus is outside of the group, then the accessible name of the group is announced when focus jumps to a control within the group.
Screen Reader support for 'MUST convey its role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
aria-required attribute on role=radiogroupsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonenonesupported

Expectation: convey the group name if it has a group name

Rationale:

A screen reader user needs to be aware of the name of group

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • The accessible name of the group is announced when entering the group.
Screen Reader support for 'MUST convey the group name if it has a group name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
aria-required attribute on role=radiogroupsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonenonesupported

Expectation: convey the boundaries of the group

Rationale:

A screen reader user needs to be aware when they enter and exit a group

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • In reading mode, there might be a stop for both the start end end of the group. When entering the group, something like "group name, group" might be announced. When leaving the group, something like "end of group" might be announced.
  • In reading mode, there might not be a stop for the start and end of the group. In this case, the screen reader might announce the group name when the user navigates to the first child and announce that the user is leaving the group when the user navigates out of the group.
  • In interaction mode, there will not be a stop for the start and end of the group. In this case, the screen reader might announce the group name when the user jumps to an interactive child and announce that the user is leaving the group when the user jumps out of the group.
Screen Reader support for 'MUST convey the boundaries of the group'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
aria-required attribute on role=radiogroupsupportedsupportedsupportedsupportedpartialpartialpartialpartialnonenonesupported