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

On this page

• Expectations
  • Support summary by expectation type
  • MUST convey an appropriate name
  • MUST convey an appropriate role
  • MUST convey the current value
  • MUST convey the current value
  • SHOULD provide shortcuts to jump to text inputs
• Related tests
• Related AT or browser issues
• Is something not right?

Expectations

Expectations are conditions that must be met for the feature to be considered as "supported". Only "MUST" expectations need to be met for minimal "support". "SHOULD" and "MAY" expectations indicates support that goes above and beyond. Note that there is not an explicit standard that dictates these expectations, and as such, they are likely opinionated. As such, a feature might not meet all "MUST" expectations but still be usable (potentially frustratingly so). Additionally, the assistive technology may provide many different commands to read, navigate, or otherwise interact with a feature. Only one command is required to pass for the expectation to be minimally supported.

Summary of support by expectation type

Summary of support by expectation and assistive technology

The screen reader MUST convey an appropriate name

Rationale: A screen reader user needs to know what to enter.

This expectation is referenced by 1 tests.

The screen reader MUST convey an appropriate role

Rationale: A screen reader user needs to know how they can interact with the element.

This expectation is referenced by 1 tests.

The screen reader MUST convey the current value

Rationale: A screen reader user needs to know the current value of the input.

This expectation is referenced by 1 tests.

The screen reader MUST convey the current value

Rationale: The user needs to know that the value was successfully changed.

This expectation is referenced by 1 tests.

The screen reader SHOULD provide shortcuts to jump to text inputs

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

This expectation is referenced by 1 tests.