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

aria-details attribute (aria)

Screen reader support level: partial (3/10)

Voice Control support level: not applicable

On this page

Identifies the element that provides a detailed, extended description for the object. See related aria-describedby.

There is poor support for aria-details, so it should not be used as the only means of conveying the relationship between an object and its detailed description. Since aria-details can only reference an element that is elsewhere on the same page, the details will likely sill be discoverable by screen reader users. Until support is more robust, it might be worth while to consider an additional indication that the object has a detailed description on the same page by way of the alt attribute or similar method.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
MUST convey the presence of aria-detailssupportednonenonenonenonenonenone
SHOULD allow the user to jump to the referenced elementnonenonenonenonenonenonenone
SHOULD allow the user to jump back to the referencing elementnonenonenonenonenonenonenone
MAY convey the boundaries of the detailssupportednonenonenonenonenonenone

Voice Control support by expectation

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

Expectation: convey the presence of aria-details

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
Screen Reader support for 'MUST convey the presence of aria-details'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
aria-details testsupportedsupportedsupportednonenonenonenonenonenonenone

Expectation: allow the user to jump to the referenced element

Rationale: If the details are not adjacent to the element with aria-details, they might find it helpful to jump directly to the details.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA
Screen Reader support for 'SHOULD allow the user to jump to the referenced element'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
aria-details testnonenonenonenonenonenonenonenonenonenone

Expectation: allow the user to jump back to the referencing element

Rationale: If the details are not adjacent to the element with aria-details, they might find it helpful to jump back so that they can continue reading the page.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA
Screen Reader support for 'SHOULD allow the user to jump back to the referencing element'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
aria-details testnonenonenonenonenonenonenonenonenonenone

Expectation: convey the boundaries of the details

Rationale: A screen reader user may find it helpful to know exactly where the details start and end.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MAY
  • Voice Control: NA
Screen Reader support for 'MAY convey the boundaries of the details'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
aria-details testsupportedsupportedsupportednonenonenonenonenonenonenone