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

select element (html)

Screen reader support level: supported

Voice Control support level: partial (8/9)

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 8 months ago and 8 months ago.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey its namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey its rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey changes in valuesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey the current valuesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
SHOULD convey the boundaries of the options within the selectsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
SHOULD convey the expanded and collapsed statesnonenonenonesupportedsupportedsupportednonesupportedsupportedsupported
SHOULD provide shortcuts to jump to this rolesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
MUST convey its namesupportednonesupportedsupportedsupported
MUST convey its rolesupportedsupportednot applicablesupportedsupported

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 might convey the name as "<role>, <name>, <value>"
  • 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
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 select element testsupportednonesupportedsupportedsupported

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 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
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 select element testsupportedsupportednot applicablesupportedsupported

Expectation: convey changes in value

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

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 new value after it has been changed
Screen Reader support for 'MUST convey changes in value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Expectation: convey the current value

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

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 name as "<role>, <name>, <value>"
Screen Reader support for 'MUST convey the current value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Expectation: convey the boundaries of the options within the select

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

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • A screen reader might convey the option name when enter thing select, 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

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

  • Screen Readers: SHOULD
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML select element testnonenonenonesupportedsupportedsupportednonesupportedsupportedsupported

Expectation: provide shortcuts to jump to this role

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

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: SHOULD
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML select element testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

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 Recognition
partial (1/5)partial (12/15)partial (4/5)partial (9/10)partial (3/5)supportedsupportednonepartial (2/5)partial (4/5)partial (2/5)none

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.