input[type="month"] 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 will announce the name (label).
• 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 "text input", "edit", "edit month", etc.
• Voice control software will let the user say something like "click text box" to focus a the input or flag the role with a number.

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

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:

• When the user enter texts, the screen reader will announce it back to them.

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: support the date picker widget and native controls

Rationale:

Users need to be able to operate the the date picker widget.

Strength of this expectation for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: MUST

Notes:

This expectation covers both the date picker widget and the embedded native controls implemented by some browsers. For example, some browsers include multiple tab stops, one each for the day, month, and year, as well as a date picker popup. Because browsers are not consistent with how these controls are implemented, they are lumped into one expectation. This expectation passes if all controls have a name, role, value, and other appropriate semantics passed. Reality check: a user can use all provided controls and successfully enter a date.

Examples:

• If implemented as a text field, this is not applicable
• If implemented as a date picker, the screen reader must convey appropriate semantics
• If implemented as multiple text inputs (one each for month, day, and year), the screen reader must convey appropriate semantics
• Voice control software will let the user activate and fill the appropriate controls

Expectation: allow data entry

Rationale:

Users need to be able to enter data

Strength of this expectation for different types of assistive technologies:

• Screen Readers: NA
• Voice Control: MUST

Examples:

• Voice control software might allow someone to dictate data into a field once it is focused.