input[type="image"] element (html)

Expectation: convey an appropriate 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 announce the button as something like "<name>, button".
• Voice control software will let the user say something like "click <name>" to activate the control.

Expectation: convey an appropriate 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 be announce the role as something like "button".
• Voice control software will let the user say something like "click button" or flag the role with a number.

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