select element (html)

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

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

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

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)

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

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.

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