RetroSearch Browse

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

Showing content from https://a11ysupport.io/tech/html/button_element below:

button_element (html) | Accessibility Support

button element (html)

Screen Reader support level: supported

Voice Control support level: partial (43/60)

On this page

About this feature

The button element represents a button labeled by its contents.

Age of results

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

Caution

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

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 MAY convey inner-text name changes when in focus none none none supported none none none none none supported partial 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 partial (3/4) supported with 2 unknown results supported supported with 3 unknown results supported with 3 unknown results MUST convey its role supported supported not applicable supported supported with 2 unknown results supported supported with 3 unknown results supported with 3 unknown results 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

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

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

Expectation: convey inner-text name changes when in focus Rationale:

The user needs to know that that the name of a control has changed after interacting with it. This may be to convey a new purpose or to convey a state change which is provided by the name.

Strength of this expectation for different types of assistive technologies:

Screen Readers: MAY
Voice Control: NA

Notes:

This expectation is only for when the button is focused by a screen reader (either keyboard focus or virtual focus). It is not meant to act like a live region.

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