RetroSearch Browse

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

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

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

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

Screen Reader support level: supported

Voice Control support level: supported with 4 unknown results

On this page

About this feature

The input element represents either an image from which a user can select a coordinate and submit the form, or alternatively a button from which the user can submit the form.

Age of results

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.

Expectations

What are 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 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 supported supported supported supported supported unknown unknown MUST convey its role supported supported not applicable supported supported 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:

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:

A screen reader might announce the button as something like "<name>, button".
Voice control software will let the user say something like "click <name>" to activate the control.

Expectation: convey its 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 this expectation for different types of assistive technologies:

Screen Readers: MUST
Voice Control: MUST

Examples:

A screen reader might be announce the role as something like "button".
Voice control software will let the user say something like "click button" or flag the role with a number.

Expectation: provide shortcuts to jump to this role Rationale:

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

Strength of this expectation for different types of assistive technologies:

Screen Readers: SHOULD
Voice Control: NA

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