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

group role (aria)

Screen reader support level: partial (19/30)

Voice Control support level: not applicable

On this page

About this feature

A set of user interface objects which are not intended to be included in a page summary or table of contents by assistive technologies.

Age of results

Results across all tests for this feature range from 9 months 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 rolepartialpartialpartialpartialpartialpartialsupportednonenonesupported
MUST convey the name if namedsupportedsupportedsupportedpartialsupportedsupportedsupportednonenonesupported
SHOULD convey the boundaries of the grouppartialpartialpartialpartialpartialpartialsupportednonenonesupported
MUST NOT convey a role or boundaries if it is not namedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
Not applicable

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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
APG 1.1 Checkbox Example (Two State)partialpartialpartialpartialpartialpartialsupportednonenonesupported

Expectation: convey the name if named

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 name if named'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
APG 1.1 Checkbox Example (Two State)supportedsupportedsupportedpartialsupportedsupportedsupportednonenonesupported

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: SHOULD
  • 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 'SHOULD convey the boundaries of the group'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
APG 1.1 Checkbox Example (Two State)partialpartialpartialpartialpartialpartialsupportednonenonesupported

Expectation: convey a role or boundaries if it is not named

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST NOT
  • Voice Control: NA

Notes:

This expectation describes the observed consistency between different screen readers. There are no standards that describe this behavior. When a group is not named but is used in certain contexts, browsers use the group role to inform the automatic generation of property values such as posinset and setsize. However, screen readers do not expose a name, role, or boundaries for the element with the group role.

Screen Reader support for 'MUST NOT convey a role or boundaries if it is not named'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
ARIA - unnamed group role testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported