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

group role (aria)

Screen reader support level: partial (21/40)

Voice Control support level: not applicable

On this page

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

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
MUST convey an appropriate role if namedpartialpartialpartialsupportednonenonesupported
MUST convey the name if namedsupportedpartialsupportedsupportednonenonesupported
MUST convey the boundaries of the grouppartialpartialpartialsupportednonenonesupported
MUST NOT convey a role or boundaries if it is not namedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

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

Expectation: convey an appropriate role if named

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

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
Screen Reader support for 'MUST convey an appropriate role if named'
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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
Screen Reader support for 'MUST 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 these expectations 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