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

button role (aria)

Screen reader support level: supported

Voice Control support level: supported

On this page

An input that allows for user-triggered actions when clicked or pressed. See related link.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
MUST convey the accessible namesupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey an appropriate rolesupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

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

Expectation: convey the accessible name

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST
Screen Reader support for 'MUST convey the accessible name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
ARIA button name from inner textsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA button name from aria-labelsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
Voice Control support for 'MUST convey the accessible name'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
ARIA button name from inner textsupportedsupportedsupportedsupportedsupported
ARIA button name from aria-labelsupportedsupportedsupportedsupportedsupported

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
Screen Reader support for 'MUST convey an appropriate role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
ARIA button name from inner textsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA button name from aria-labelsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
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 button name from inner textsupportedsupportednot applicablesupportedsupported
ARIA button name from aria-labelsupportedsupportednot applicablesupportedsupported