38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
[Back to 1 Perceivable index](index.html)
|
|
|
|
# 1.3.5 Identify Input Purpose
|
|
|
|
- Level: AA
|
|
- Guideline: 1.3 Adaptable
|
|
- Principle: 1 Perceivable
|
|
|
|
## What it is
|
|
|
|
The purpose of each input field collecting information about the user can be programmatically determined when:
|
|
|
|
- The input field serves a purpose identified in the Input Purposes for user interface components section; and
|
|
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
|
|
|
|
## How to test
|
|
|
|
- Check: The input field serves a purpose identified in the Input Purposes for user interface components section; and
|
|
- Check: The content is implemented using technologies with support for identifying the expected meaning for form input data.
|
|
- Use the sufficient techniques below as acceptable methods when applicable.
|
|
- Confirm none of the common failures apply.
|
|
|
|
## Sufficient techniques (W3C)
|
|
|
|
- H98: Using HTML autocomplete attributes
|
|
|
|
## Common failures (W3C)
|
|
|
|
- F107: Failure of Success Criterion 1.3.5 due to incorrect autocomplete attribute values
|
|
|
|
## Resources
|
|
|
|
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#identify-input-purpose
|
|
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/identify-input-purpose.html
|
|
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#identify-input-purpose
|
|
|
|
[Back to 1 Perceivable index](index.html)
|