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

table element (html)

Screen reader support level: supported

Voice Control support level: not applicable

On this page

About this feature

Age of results

Results across all tests for this feature range from 2 months ago to 2 years ago. Detailed dates and version information can be found in associated tests.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey an appropriate rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the boundaries of the tablesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

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

Expectation: convey an appropriate role

Rationale: A user needs to be aware that they are navigating a table.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • A screen reader might announce an element as something like "<name>, <role>"
  • A screen reader might imply the role by the presence of certain context roles
  • Voice Control software might let the user say something like "click, <role>".
  • Voice Control software might let the user say something like "show numbers", and interactive roles will be flagged with numbers.

Expectation: convey the boundaries of the table

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

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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

Related features

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

td element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech Recognition
not applicablesupportedsupportedsupportedsupportedsupportednot applicablenot applicablenot applicablesupportedsupportednot applicable

th element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech Recognition
not applicablesupportedsupportedsupportedsupportedsupportednot applicablenot applicablenot applicablepartial (3/4)supportednot applicable