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.

select element (html)

Screen Reader support level: partial (41/44)

Voice Control support level: partial (10/15)

On this page

About this feature

Age of results

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

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

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
MUST convey its namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey its rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey changes in valuesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonesupportedpartial
MUST convey the current valuesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonesupportedsupported
SHOULD convey the boundaries of the options within the selectsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
SHOULD convey the expanded and collapsed statessupportedsupportedsupportedsupportedsupportedsupportedsupportednonesupportedsupportedsupported
SHOULD provide shortcuts to jump to this rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech RecognitionWindows Voice Access
ChromeChromeSafariSafariEdgeChromeEdgeChrome
MUST convey its namesupportednonesupportedsupportedsupportedsupportedunknownunknown
MUST convey its rolesupportedsupportednot applicablesupportedsupportedsupportedunknownunknown

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: 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:

  • A screen reader might convey the name as something like "<role>, <name>, <value>" (order varies by screen reader and settings)
  • Voice control software might allow the user to say "click <name>" to focus the select element
Screen Reader support for 'MUST convey its name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
Voice Control support for 'MUST convey its name'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech RecognitionWindows Voice Access
ChromeChromeSafariSafariEdgeChromeEdgeChrome
HTML select element testsupportednonesupportedsupportedsupportedsupportedunknownunknown

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: MUST

Examples:

  • A screen reader might convey the select as a select or a combo box
  • Voice control software might allow the user to say "click list box" to focus the select element
Screen Reader support for 'MUST convey its role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
Voice Control support for 'MUST convey its role'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech RecognitionWindows Voice Access
ChromeChromeSafariSafariEdgeChromeEdgeChrome
HTML select element testsupportedsupportednot applicablesupportedsupportedsupportedunknownunknown

Expectation: convey changes in value

Rationale:

The user needs to know that the value was successfully changed.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might announce the new value after it has been changed
Screen Reader support for 'MUST convey changes in value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonesupportedpartial

Expectation: convey the current value

Rationale:

A screen reader user needs to know the current value of the input.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • A screen reader might convey the value as something like "<role>, <name>, <value>" (order varies by screen reader and settings)
Screen Reader support for 'MUST convey the current value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportednonesupportedsupported

Expectation: convey the boundaries of the options within the select

Rationale:

The user needs to know when they enter and leave the options.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA

Examples:

  • A screen reader might convey the option name when entering, and "out of select" when exiting
  • A screen reader might convey information about the position in the options, such as "4 of 4" to indicate the start and end of the options
Screen Reader support for 'SHOULD convey the boundaries of the options within the select'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Expectation: convey the expanded and collapsed states

Rationale:

The user might find it helpful to know if the select is open or closed.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA

Examples:

  • A screen reader might convey the collapsed state as "4 of 4" and the expanded state as
  • A screen reader will usually imply the expanded state by sending focus to the option list. When the user leaves the option list, the select becomes collapsed.
Screen Reader support for 'SHOULD convey the expanded and collapsed states'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportednonesupportedsupportedsupported

Expectation: provide shortcuts to jump to this role

Rationale:

Screen reader users might want to quickly navigate to elements of this type.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA

Examples:

  • A screen reader might provide a keyboard shortcut to jump to the next form control or provide a list of all form controls
Screen Reader support for 'SHOULD provide shortcuts to jump to this role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Related features

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

option element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech RecognitionWindows Voice AccessWindowsMaciOSAndroid Keyboard
partial (1/6)supported with 1 unknown resultpartial (4/6)partial (14/16)partial (3/6)supported with 1 unknown resultsupported with 1 unknown resultno known supportpartial (2/6)partial (4/6)partial (2/6)partial (4/10)unknownunknownunknownunknownunknown

We are missing data on some combinations.

optgroup element (html)

DragonJAWSNarratorNVDAOrcaTalkBackVoice AccessVC iOSVC MacOSVoiceOver (iOS)VoiceOver (macOS)Speech RecognitionWindows Voice AccessWindowsMaciOSAndroid Keyboard
unknownno known supportno known supportpartial (3/10)no known supportpartial (1/4)unknownunknownunknownpartial (2/4)partial (1/4)unknownunknownunknownunknownunknownunknown