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

fieldset element (html)

Screen reader support level: partial (28/60)

Voice Control support level: not applicable

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 6 months ago to 7 months ago. Detailed dates and version information can be found in associated tests.

Failing and partial results are between 7 months ago and 7 months ago.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey an appropriate rolesupportedsupportedsupportednonepartialpartialsupportednonesupportedsupported
MUST convey an appropriate namepartialpartialpartialpartialpartialpartialsupportedpartialsupportedsupported
MUST convey the boundaries of the elementsupportedsupportedsupportednonepartialpartialsupportednonepartialsupported

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 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 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 an appropriate name

Rationale: A screen reader user needs to know what to enter.

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 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 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
Screen Reader support for 'MUST convey the boundaries of the element'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
aria-required attribute on each HTML radio button in a fieldsetsupportedsupportedsupportednonepartialpartialsupportednonepartialsupported
The html required attribute on each HTML radio button in a fieldsetsupportedsupportedsupportednonepartialpartialsupportednonepartialsupported

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 Recognition
not applicablepartialpartialpartialsupportedpartialnot applicablenot applicablenot applicablesupportedsupportednot applicable