Important: This website does not attempt to establish a standard for how assistive technologies must behave. Read the FAQ for more information. Additionally, this is a work in progress. Please submit feedback or suggestions.

figure element (html)

Screen Reader support level: partial (72/132)

On this page

About this feature

Age of results

Results across all tests for this feature range from 4 years ago to 6 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 6 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

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"
Screen Reader support for 'MUST convey its role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
Figure test 1 - name from figcaptionsupportedsupportedsupportednonenoneunknownnonesupportednonenonesupported
Figure test 2 - name from authorsupportedsupportedsupportednonenoneunknownnonesupportednonenonesupported
Figure test 3 - no figcaptionsupportedsupportedsupportednonenoneunknownnonesupportednonenonenone

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
Screen Reader support for 'MUST convey its name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
Figure test 1 - name from figcaptionsupportedsupportedsupportednonenoneunknownnonesupportednonenonesupported
Figure test 2 - name from authorsupportedsupportedsupportednonenoneunknownnonesupportednonenonesupported
Figure test 3 - no figcaptionsupportedsupportedsupportednonenoneunknownnonesupportednonenonenone

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
Screen Reader support for 'MUST convey the boundaries of the element'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
Figure test 1 - name from figcaptionsupportedsupportedsupportednonenoneunknownnonesupportednonenonesupported
Figure test 2 - name from authorsupportedsupportedsupportednonenoneunknownnonesupportednonenonesupported
Figure test 3 - no figcaptionsupportedsupportedsupportednonenoneunknownnonesupportednonenonenone

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.
Screen Reader support for 'MUST allow navigating content'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
Figure test 1 - name from figcaptionsupportedsupportedsupportedsupportedsupportedunknownsupportedsupportedsupportedsupportedsupported
Figure test 2 - name from authorsupportedsupportedsupportedsupportedsupportedunknownsupportedsupportedsupportedsupportedsupported
Figure test 3 - no figcaptionsupportedsupportedsupportedsupportedsupportedunknownsupportedsupportedsupportedsupportedsupported

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 RecognitionWindows Voice AccessWindowsMaciOSAndroid Keyboard
unknownpartial (9/19)partial (2/7)partial (4/19)partial (4/7)partial (2/7)unknownunknownunknownpartial (2/7)partial (2/7)unknownunknownunknownunknownunknownunknown

We are missing data on some combinations.

TestLast update
Figure test 1 - name from figcaption2021-07-29
Figure test 2 - name from author2021-07-29
Figure test 3 - no figcaption2021-07-29

Is something not right?

We use our GitHub repository to manage our issue tracking. Please provide as much information as you can for issues, and please leave the id in the issue title intact.

Create an issue for this feature