Screen Reader support level: supported
Voice Control support level: partial (14/23)
On this page About this feature Age of resultsResults 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.
CautionFailing or partial results may be out of date. The oldest result is from 6 years ago. Consider running the associated tests and contributing results.
Expectations Screen Reader support by expectation Expectation JAWS Narrator NVDA Orca TalkBack VoiceOver (iOS) VoiceOver (macOS) Chrome Edge Firefox Edge Chrome Edge Firefox Firefox Chrome Safari Safari MUST convey its name supported supported supported supported supported supported supported supported supported supported supported MUST convey its role supported supported supported supported supported supported supported supported supported supported supported MUST convey the current value supported supported supported supported supported supported supported supported supported supported supported MUST convey changes in value supported supported supported supported supported supported supported supported supported supported supported SHOULD provide shortcuts to jump to this role supported supported supported supported supported supported supported supported supported supported supported Voice Control support by expectation Expectation Dragon Naturally Speaking Voice Access (Android) Voice Control (iOS) Voice Control (MacOS) Windows Speech Recognition Windows Voice Access Chrome Chrome Safari Safari Edge Chrome Edge Chrome MUST convey its name supported none supported supported none supported unknown unknown MUST convey its role supported supported not applicable supported supported supported unknown unknown MUST allow data entry supported supported supported supported unknown supported unknown unknown 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: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 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:A screen reader user needs to know the current value of the input.
Strength of this expectation for different types of assistive technologies:The user needs to know that the value was successfully changed.
Strength of this expectation for different types of assistive technologies:Screen reader users might want to quickly navigate to elements of this type.
Strength of this expectation for different types of assistive technologies:Users need to be able to enter data
Strength of this expectation for different types of assistive technologies: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