Test: HTML select element test

Expectation for the disabled attribute: convey the disabled state - applied to the option element

This expectation is applied to the option element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the disabled attribute feature.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: MAY

Examples:

• Screen readers might convey the disabled state by announcing "disabled", "unavailable", or "dimmed"
• Screen readers might convey the disabled state of certain embedded controls, such as the option element, by skipping it when navigating embedded controls
• Voice control software might not include the element in operations, for example it might not flag the element with a number or respond to name commands

Grading method:

Just one of the listed commands must pass for the expectation to pass.

Expectation for the disabled attribute: convey the disabled state - applied to the optgroup element

This expectation is applied to the optgroup element. Expectations and results might differ when the the feature is applied to different roles.

This expectation is from the disabled attribute feature.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: MAY

Examples:

• Screen readers might convey the disabled state by announcing "disabled", "unavailable", or "dimmed"
• Screen readers might convey the disabled state of certain embedded controls, such as the option element, by skipping it when navigating embedded controls
• Voice control software might not include the element in operations, for example it might not flag the element with a number or respond to name commands

Grading method:

Just one of the listed commands must pass for the expectation to pass.

Expectation for the optgroup element: convey its name

This expectation is from the optgroup element feature.

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

Grading method:

Just one of the listed commands must pass for the expectation to pass.

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.

Expectation for the optgroup element: convey its role

This expectation is from the optgroup element feature.

Rationale:

A screen reader user needs to know that options are in a group.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: NA

Examples:

• A screen reader might convey the group role.

Grading method:

Just one of the listed commands must pass for the expectation to pass.

Expectation for the optgroup element: convey the boundaries of the element

This expectation is from the optgroup element feature.

Rationale:

A user needs to know when they enter and exit an element

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: NA

Examples:

• 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

Grading method:

All of the listed commands must pass for the expectation to pass.

Expectation for the option element: convey its name

This expectation is from the option element feature.

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

Examples:

• 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.

Grading method:

Just one of the listed commands must pass for the expectation to pass.

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.

Expectation for the option element: convey its role

This expectation is from the option element feature.

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

Grading method:

Just one of the listed commands must pass for the expectation to pass.

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

This expectation is from the option element feature.

Rationale:

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

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MAY
• Voice Control: NA

Examples:

• A screen reader might announce "choose <2 of 10>" when navigating through a list of options

Grading method:

Just one of the listed commands must pass for the expectation to pass.

Expectation for the select element: convey its name

This expectation is from the select element feature.

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

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

Grading method:

Just one of the listed commands must pass for the expectation to pass.

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.