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.

fieldset element (html)

Screen reader support level: partial (54/67)

Voice Control support level: unknown

On this page

About this feature

The fieldset element represents a set of form controls (or other content) grouped together, optionally with a caption.

Age of results

Results across all tests for this feature range from 2 years ago to 4 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 4 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 rolesupportedsupportedsupportednonesupportedsupportedsupportedsupportednonesupportedsupported
MUST convey its namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the boundaries of the elementsupportedsupportedsupportednonesupportedsupportedpartialsupportednonepartialsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech RecognitionWindows Voice Access
ChromeChromeSafariSafariEdgeChromeEdgeChrome
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 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 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 convey the fieldset as "<role> <name-from-legend>"

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

Related features

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

legend element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech RecognitionWindows Voice Access
unknownsupported with 1 unknown resultsupported with 1 unknown resultsupported with 1 unknown resultsupported with 1 unknown resultsupported with 1 unknown resultunknownunknownunknownsupported with 1 unknown resultsupported with 1 unknown resultunknownunknown

We are missing data on some combinations.