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

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

Screen reader support level: partial (22/48)

Voice Control support level: partial (10/16)

On this page

About this feature

Age of results

Results across all tests for this feature range from 2 months ago to 5 months ago. Detailed dates and version information can be found in associated tests.

Failing and partial results are between 5 months ago and 5 months ago.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey an appropriate namesupportedsupportedpartialsupportedsupportedpartialpartialsupportedsupportedpartial
MUST convey an appropriate rolesupportedsupportedpartialsupportedpartialpartialpartialsupportedsupportedpartial
MUST convey the current valuepartialsupportedpartialsupportedpartialpartialpartialnonesupportedpartial
MUST convey changes in valuesupportedsupportedsupportednonesupportedsupportedpartialnonenonesupported
SHOULD provide shortcuts to jump to this rolesupportedsupportedsupportedsupportednonesupportednonesupportedsupportedsupported
MUST support the date picker widget and native controlspartialnot applicablepartialsupportedpartialpartialsupportedpartialnonenot applicable

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
MUST convey an appropriate namenonesupportedsupportedsupportedsupported
MUST convey an appropriate rolenonesupportednot applicablesupportedsupported
MUST support the date picker widget and native controlsnonesupportedsupportednot applicablepartial
MUST allow data entrynonenot applicablenot applicablesupportednone

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 will announce the name (label).
  • Voice control software will let the user say something like "click <name>" to activate the control.
Screen Reader support for 'MUST convey an appropriate name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html time input testsupportedsupportedpartialsupportedsupportedpartialpartialsupportedsupportedpartial
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 time input testnonesupportedsupportedsupportedsupported

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 "text input", "edit", "edit time", 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.
Screen Reader support for 'MUST convey an appropriate role'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html time input testsupportedsupportedpartialsupportedpartialpartialpartialsupportedsupportedpartial
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 time 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 time input testpartialsupportedpartialsupportedpartialpartialpartialnonesupportedpartial

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

Examples of assistive technologies support this expectation:

  • When the user enter texts, the screen reader will announce it back to them.
Screen Reader support for 'MUST convey changes in value'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html time input testsupportedsupportedsupportednonesupportedsupportedpartialnonenonesupported

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 time input testsupportedsupportedsupportedsupportednonesupportednonesupportedsupportedsupported

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.

Examples of assistive technologies support this expectation:

  • 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
Screen Reader support for 'MUST support the date picker widget and native controls'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
Basic html time input testpartialnot applicablepartialsupportedpartialpartialsupportedpartialnonenot applicable
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 time input testnonesupportedsupportednot applicablepartial

Expectation: allow data entry

Rationale: Users need to be able to enter data

Strength of these expectations for different types of assistive technologies:

  • Screen Readers: NA
  • Voice Control: MUST

Examples of assistive technologies support this expectation:

  • Voice control software might allow someone to dictate data into a field once it is focused.
Voice Control support for 'MUST allow data entry'
TestDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
Basic html time input testnonenot applicablenot applicablesupportednone