Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://a11ysupport.io/tech/html/input(type-time)_element below:

input(type-time)_element (html) | Accessibility Support

Screen Reader support level: partial (43/53)

Voice Control support level: partial (10/28)

• About this feature
• Age of results
• Expectations
  • convey its name
  • convey its role
  • convey the current value
  • convey changes in value
  • provide shortcuts to jump to this role
  • support the date picker widget and native controls
  • allow data entry
• Related tests
• Is something not right?

Results across all tests for this feature range from 4 years ago to 6 years ago. Detailed dates and version information can be found in associated tests.

Failing or partial results may be out of date. The oldest result is from 6 years ago. Consider running the associated tests and contributing results.

What are expectations?

A screen reader user needs to know what to enter.

• Screen Readers: MUST
• Voice Control: MUST

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.

• A screen reader will announce the name (label).
• Voice control software will let the user say something like "click <name>" to activate the control.

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.

• Screen Readers: MUST
• Voice Control: MUST

• 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.

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

• Screen Readers: MUST
• Voice Control: NA

The user needs to know that the value was successfully changed.

• Screen Readers: MUST
• Voice Control: NA

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

Screen reader users might want to quickly navigate to elements of this type.

• Screen Readers: SHOULD
• Voice Control: NA

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

• Screen Readers: MUST
• Voice Control: MUST

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.

• 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

Users need to be able to enter data

• Screen Readers: NA
• Voice Control: MUST

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

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4