input[type="email"] element (html)
Screen reader support level: partial (38/40)
Voice Control support level: partial (13/14)
On this page
About this feature
Age of results
Results across all tests for this feature range from 4 months ago to 10 months ago. Detailed dates and version information can be found in associated tests.
Failing and partial results are between 10 months ago and 10 months ago.
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 its name | supported | supported | supported | supported | supported | supported | supported | supported | supported | partial |
| MUST convey its role | supported | supported | supported | supported | supported | supported | supported | supported | supported | partial |
| MUST convey the current value | 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 |
| SHOULD provide shortcuts to jump to this role | supported | supported | supported | supported | supported | supported | supported | supported | supported | partial |
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 its name | supported | none | supported | supported | supported |
| MUST convey its role | supported | supported | not applicable | supported | supported |
| MUST allow data entry | supported | supported | supported | supported | supported |
Expectation: convey its 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
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 of assistive technologies support this expectation:
- A screen reader will announce the name (label).
- 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 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 "text input", "edit", "edit text", "email" etc. Actually announcing "email" is not required.
- 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.
| Test | JAWS | Narrator | NVDA | Orca | TalkBack | VoiceOver (iOS) | VoiceOver (macOS) | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | IE | Firefox | Edge | Chrome | Firefox | Firefox | Chrome | Safari | Safari | |
| Basic html email input test | supported | supported | supported | supported | supported | supported | supported | supported | supported | partial |
| Test | Dragon Naturally Speaking | Voice Access (Android) | Voice Control (iOS) | Voice Control (MacOS) | Windows Speech Recognition |
|---|---|---|---|---|---|
| Chrome | Chrome | Safari | Safari | Chrome | |
| Basic html email input test | supported | supported | not applicable | supported | supported |
Expectation: convey the current value
Rationale: A screen reader user needs to know the current value of the input.
Strength of these expectations for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: NA
Expectation: convey changes in value
Rationale: The user needs to know that the value was successfully changed.
Strength of these expectations for different types of assistive technologies:
- Screen Readers: MUST
- Voice Control: NA
Examples of assistive technologies support this expectation:
- When the user enter texts, the screen reader will announce it back to them.
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 email input test | supported | supported | supported | supported | supported | supported | supported | supported | supported | partial |
Expectation: allow data entry
Rationale: Users need to be able to enter data
Strength of these expectations for different types of assistive technologies:
- Screen Readers: NA
- Voice Control: MUST
Examples of assistive technologies support this expectation:
- Voice control software might allow someone to dictate data into a field once it is focused.