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

dialog role (aria)

Screen reader support level: partial (24/30)

Voice Control support level: not applicable

On this page

A dialog is a descendant window of the primary window of a web application. For HTML pages, the primary application window is the entire web document, i.e., the body element.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver for iOSVoiceOver for macOS
MUST convey the dialog rolesupportedsupportedsupportedsupportednonesupportedsupported
MUST convey the name of the dialogsupportedsupportedsupportedsupportednonesupportedsupported
MUST convey the boundaries of the dialogsupportedpartialsupportedpartialnonepartialsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access for AndroidVoice Control for iOSVoice Control for MacOS
Not applicable

Expectation: convey the dialog role

Rationale: Users must be made aware of the dialog context.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
ATBrowserHas Support
Dragon Naturally SpeakingGoogle Chromenot applicable
JAWSGoogle Chromesupported
JAWSInternet Explorersupported
JAWSFirefox (desktop)supported
NarratorMicrosoft Edgesupported
NVDAGoogle Chromesupported
NVDAFirefox (desktop)supported
OrcaFirefox (desktop)supported
TalkBackGoogle Chrome (android)none
Voice Access for AndroidGoogle Chrome (android)not applicable
Voice Control for iOSSafari (iOS)not applicable
Voice Control for MacOSSafari (macOS)not applicable
VoiceOver for iOSSafari (iOS)supported
VoiceOver for macOSSafari (macOS)supported

This expectation is referenced by 1 tests.

Tests that reference this expectation
Test nameScreen Reader supportVoice Control support
APG 1.1 modal dialog examplepartial (29/40)not applicable

Expectation: convey the name of the dialog

Rationale: Users need to know the purpose of the dialog.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
ATBrowserHas Support
Dragon Naturally SpeakingGoogle Chromenot applicable
JAWSGoogle Chromesupported
JAWSInternet Explorersupported
JAWSFirefox (desktop)supported
NarratorMicrosoft Edgesupported
NVDAGoogle Chromesupported
NVDAFirefox (desktop)supported
OrcaFirefox (desktop)supported
TalkBackGoogle Chrome (android)none
Voice Access for AndroidGoogle Chrome (android)not applicable
Voice Control for iOSSafari (iOS)not applicable
Voice Control for MacOSSafari (macOS)not applicable
VoiceOver for iOSSafari (iOS)supported
VoiceOver for macOSSafari (macOS)supported

This expectation is referenced by 1 tests.

Tests that reference this expectation
Test nameScreen Reader supportVoice Control support
APG 1.1 modal dialog examplepartial (29/40)not applicable

Expectation: convey the boundaries of the dialog

Rationale: Users need to know when they enter and exit a dialog.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
ATBrowserHas Support
Dragon Naturally SpeakingGoogle Chromenot applicable
JAWSGoogle Chromesupported
JAWSInternet Explorersupported
JAWSFirefox (desktop)supported
NarratorMicrosoft Edgepartial
NVDAGoogle Chromesupported
NVDAFirefox (desktop)supported
OrcaFirefox (desktop)partial
TalkBackGoogle Chrome (android)none
Voice Access for AndroidGoogle Chrome (android)not applicable
Voice Control for iOSSafari (iOS)not applicable
Voice Control for MacOSSafari (macOS)not applicable
VoiceOver for iOSSafari (iOS)partial
VoiceOver for macOSSafari (macOS)supported

This expectation is referenced by 1 tests.

Tests that reference this expectation
Test nameScreen Reader supportVoice Control support
APG 1.1 modal dialog examplepartial (29/40)not applicable