button 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

Examples:

• 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 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 be announce the role as something like "button".
• Voice control software will let the user say something like "click button".

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

Expectation: convey inner-text name changes when in focus

Rationale:

The user needs to know that that the name of a control has changed after interacting with it. This may be to convey a new purpose or to convey a state change which is provided by the name.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MAY
• Voice Control: NA

Notes:

This expectation is only for when the button is focused by a screen reader (either keyboard focus or virtual focus). It is not meant to act like a live region.