input[type="datetime-local"] 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

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

Expectation: convey the current value

Rationale: A screen reader user needs to know the current value of the input.

Strength of these expectations 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 these expectations for different types of assistive technologies:

• Screen Readers: MUST
• Voice Control: NA

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

Expectation: support the date picker widget and native controls

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

Strength of these expectations 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.