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

figure element (html)

Screen reader support level: partial (72/133)

Voice Control support level: unknown

On this page

About this feature

Age of results

Results across all tests for this feature range from a year ago to 3 years 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 3 years ago. Consider running the associated tests and contributing results.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
MUST convey its rolesupportedsupportedsupportednonenoneunknownnonesupportednonenonepartial (2/3)
MUST convey its namesupportedsupportedsupportednonenoneunknownnonesupportednonenonepartial (2/3)
MUST convey the boundaries of the elementsupportedsupportedsupportednonenoneunknownnonesupportednonenonepartial (2/3)
MUST allow navigating contentsupportedsupportedsupportedsupportedsupportedunknownsupportedsupportedsupportedsupportedsupported

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 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 this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might convey the role as something like "figure"

Expectation: convey its name

Rationale:

A screen reader user needs to know what to enter.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might source the name from the "figcapion", "aria-label" attribute, "aria-labelledby" attribute, or "title" attribute

Expectation: convey the boundaries of the element

Rationale:

A user needs to know when they enter and exit an element

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might announce the role of the element when entering and say something like "leaving" when exiting.
  • A screen reader might not explicitly announce entering and existing the element, but instead imply that the is in the containing object by conveying the roles of required children (options in a listbox for example).
  • A screen reader might announce position in set information such as "1 of 6".
  • A screen reader might not convey boundaries if the content fits on a single line

Expectation: allow navigating content

Rationale:

A user needs to be able to navigate the content

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might allow reading-mode navigation, such as reading line-by-line.

Related features

These are features that are usually used in combination with this feature.

figcaption element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech Recognition
unknownpartial (9/19)partial (2/7)partial (4/19)partial (4/7)partial (2/7)unknownunknownunknownpartial (2/7)partial (2/7)unknown

We are missing data on some combinations.