1.3.5: Identify Input Purpose [AA]
Description
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.
Sufficient Techniques
Sufficient Techniques for Success Criterion 1.3.6
Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques.
- Programmatically indicating the purpose of icons, regions and user interface components
- ARIA11: Using ARIA landmarks to identify regions of a page
- Using microdata to markup user interface components (future link)
Advisory Techniques
Advisory Techniques for Success Criterion 1.3.6
- Enabling user agents to find the version of the content that best fits their needs
- Using semantics to identify important features (e.g., coga-simplification="simplest")
- Using aria-invalid and aria-required
Failures
Failures for Success Criterion 1.4.1
- F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image
- F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision
- F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only