button element (html)
Screen reader support level: supported
Voice Control support level: supported
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 5 months ago to 8 months ago. Detailed dates and version information can be found in associated tests.
Expectations
Screen Reader support by expectation
| Expectation | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | IE | Firefox | Edge | Chrome | Firefox | Firefox | Chrome | Safari | Safari | |
| MUST convey an appropriate name | supported | supported | supported | supported | supported | supported | supported | supported | supported | supported |
| MUST convey an appropriate role | 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 |
Voice Control support by expectation
| Expectation | Dragon Naturally Speaking | Voice Access (Android) | Voice Control (iOS) | Voice Control (MacOS) | Windows Speech Recognition |
|---|---|---|---|---|---|
| Chrome | Chrome | Safari | Safari | Chrome | |
| MUST convey an appropriate name | supported | supported | supported | supported | supported |
| MUST convey an appropriate role | supported | supported | not applicable | supported | supported |
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
Examples of assistive technologies support this expectation:
- 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 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 something like "button".
- Voice control software will let the user say something like "click button".
| Test | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | IE | Firefox | Edge | Chrome | Firefox | Firefox | Chrome | Safari | Safari | |
| Basic HTML button test | supported | supported | supported | supported | supported | supported | supported | supported | supported | supported |
| Test | Dragon Naturally Speaking | Voice Access (Android) | Voice Control (iOS) | Voice Control (MacOS) | Windows Speech Recognition |
|---|---|---|---|---|---|
| Chrome | Chrome | Safari | Safari | Chrome | |
| Basic HTML button test | supported | supported | not applicable | supported | supported |
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
| Test | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | IE | Firefox | Edge | Chrome | Firefox | Firefox | Chrome | Safari | Safari | |
| Basic HTML button test | supported | supported | supported | supported | supported | supported | supported | supported | supported | supported |