Notice: This is a work in progress. Please submit feedback or suggestions.

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

Screen reader support level: partial (24/49)

Voice Control support level: partial (9/14)

On this page

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
MUST convey an appropriate namesupportedsupportedpartial (1/2)partialsupportedsupportedpartial
MUST convey an appropriate rolesupportedsupportedpartialnonesupportedsupportedpartial
MUST convey the current valuepartial (1/3)supportedpartialpartialnonesupportedsupported
MUST convey changes in valuesupportednonesupportedpartialnoneunknownsupported
SHOULD provide shortcuts to jump to this rolesupportedsupportednonenonesupportedsupportedsupported
MUST support the date picker widget and native controlspartialsupportedpartialpartialpartialnoneunknown

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
MUST convey an appropriate namenonesupportedsupportedsupportedsupported
MUST convey an appropriate rolenonesupportednot applicablesupportedsupported
MUST support the date picker widget and native controlsnonesupportedsupportedunknownpartial

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
Screen Reader support for 'MUST convey an appropriate name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html date input testsupportedsupportedsupportedsupportedpartialsupportedpartialsupportedsupportedpartial
Voice Control support for 'MUST convey an appropriate name'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
Basic html date input testnonesupportedsupportedsupportedsupported

Expectation: convey an appropriate role

Rationale: A screen reader user needs to know that they can enter text.

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: MUST
Screen Reader support for 'MUST convey an appropriate role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html date input testsupportedsupportedsupportedsupportedpartialpartialnonesupportedsupportedpartial
Voice Control support for 'MUST convey an appropriate role'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
Basic html date input testnonesupportednot applicablesupportedsupported

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
Screen Reader support for 'MUST convey the current value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html date input testpartialsupportedpartialsupportedpartialpartialpartialnonesupportedsupported

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
Screen Reader support for 'MUST convey changes in value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html date input testsupportedsupportedsupportednonesupportedsupportedpartialnoneunknownsupported

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
Screen Reader support for 'SHOULD provide shortcuts to jump to this role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html date input testsupportedsupportedsupportedsupportednonenonenonesupportedsupportedsupported

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.

Screen Reader support for 'MUST support the date picker widget and native controls'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html date input testpartialnot applicablepartialsupportedpartialpartialpartialpartialnoneunknown
Voice Control support for 'MUST support the date picker widget and native controls'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
Basic html date input testnonesupportedsupportedunknownpartial