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

option element (html)

Screen reader support level: partial (39/50)

Voice Control support level: partial (8/23)

On this page

About this feature

Age of results

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

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

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey its namesupportedpartial (1/2)supportedsupportedsupportedsupportedsupportedsupportedpartial (1/2)partial (1/2)
MUST convey its rolesupportedpartial (1/2)supportedsupportedsupportedsupportedpartial (1/2)supportedsupportedpartial (1/2)
MUST convey the value of the option when used in a datalist contextsupportednonesupportednonesupportednonenonesupportedsupportednone
MAY convey information about the position the option in the listpartial (1/2)nonesupportedsupportedsupportedsupportednonenonesome partial supportnone

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
MUST convey its namesome partial supportsupportednonepartial (1/2)none
MUST convey its rolepartial (1/2)supportednot applicablepartial (1/2)none
MUST convey the value of the option when used in a datalist contextnonesupportednonenonenone

Expectation: convey its 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: MUST

Notes: For form inputs - commands to read line by line (down and up arrows in most windows screen readers) will not always result in the name being explicitly conveyed when the virtual focus is moved to an input where the label is visually displayed and programmatically associated with the input. This is acceptable because the name is implied by the fact that it should be naturally found in the reading order. Some screen readers choose to not convey the name in these cases, likely in an effort to reduce verbosity.

Examples of assistive technologies support this expectation:

  • A screen reader will announce the name of the option (if present) in addition to the value.
  • Voice control software will let the user say something like "choose <name>" after saying something like "show choices" to pick the option.
Screen Reader support for 'MUST convey its name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML input with datalist testsupportednonesupportedsupportedsupportedsupportedsupportedsupportednonenone
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
Voice Control support for 'MUST convey its name'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
HTML input with datalist testnonesupportednonenonenone
HTML select element testpartialsupportednonesupportednone

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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST

Examples of assistive technologies support this expectation:

  • A screen reader might announce "option" as the role.
  • A screen reader might not announce a role because the role is implied by the role of a select element, combo box, or listbox.
  • A screen reader might not announce a role because the role is implied by the announcement of auto complete or suggestions.
  • Voice control software will let the user say something like "move down <n>" or "move up <n>" to select an option.
Screen Reader support for 'MUST convey its role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML input with datalist testsupportednonesupportedsupportedsupportedsupportedpartialsupportedsupportednone
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
Voice Control support for 'MUST convey its role'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
HTML input with datalist testnonesupportednot applicablenonenone
HTML select element testsupportedsupportednot applicablesupportednone

Expectation: convey the value of the option when used in a datalist context

Rationale: When in a datalist context, both the name and value are displayed, so the user needs to be aware of both.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST

Examples of assistive technologies support this expectation:

  • A screen reader will announce the value of the option in addition to the name.
  • Voice control software will let the user say something like "choose <value>" to pick an option.
Screen Reader support for 'MUST convey the value of the option when used in a datalist context'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML input with datalist testsupportednonesupportednonesupportednonenonesupportedsupportednone
Voice Control support for 'MUST convey the value of the option when used in a datalist context'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
HTML input with datalist testnonesupportednonenonenone

Expectation: convey information about the position the option in the list

Rationale: When user should be able to determine how many options are in the list and where they are in the list

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MAY
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • A screen reader might announce "choose <2 of 10>" when navigating through a list of options
Screen Reader support for 'MAY convey information about the position the option in the list'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML input with datalist testsupportednonesupportedsupportedsupportedsupportednonenonenonenone
HTML select element testnonenonesupportedsupportedsupportedsupportednonenonepartialnone

Related features

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

select element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech Recognition
supportedsupportedsupportedsupportedsupportedsupportedpartial (1/2)supportedsupportedsupportedsupportedsupported

optgroup element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech Recognition
not applicablepartial (3/9)partial (1/3)partial (3/6)nonepartial (1/3)not applicablenot applicablenot applicablepartial (1/3)partial (1/3)not applicable

We are missing data on some combinations.