Identify Input Purpose
Summary:
WCAG 1.3.5, "Identify Input Purpose," is about enhancing user experience and accessibility by helping technologies understand the purpose of input fields in forms and content. This guideline is particularly beneficial for users who rely on assistive technologies, like screen readers, and for those who benefit from automated form filling.
What:
The criterion requires that the purpose of each input field collecting information about the user is programmatically determinable. This means that fields in forms, such as those for names, addresses, phone numbers, and the like, should be coded so that assistive technologies can recognize what kind of data is expected.
Why:
When input fields are clearly identified, assistive technologies can provide more relevant assistance, such as autofilling forms based on previously stored user data. This not only speeds up the interaction for users but also reduces the likelihood of errors, making digital environments more accessible and efficient.
Examples and Scenarios:
- Registration Forms: A sign-up form should have its fields (like first name, last name, email, and password) properly tagged so that screen readers can announce what type of information is required.
- Checkout Process: E-commerce sites should ensure that fields for delivery address, contact information, and payment details are clearly identified for assistive tools.
- Login Pages: Fields for username and password should be programmatically labeled to facilitate easier and more secure login through assistive technologies.
How to Comply:
- Websites: Use HTML5 input field types and ARIA labels to define the purpose of each field. Ensure that forms are properly labeled and structured.
- Mobile Apps: Design forms in apps with clear identification for each input field, allowing assistive technologies to recognize and interact with them effectively.
- Software Applications: In applications requiring user input, label all data fields appropriately to assist users in understanding and completing them.
Exceptions:
- Non-Standard and Unique Input Fields: Inputs that require unique or non-standard user information may not have programmatically determinable purposes.
- Technical Limitations: Certain technology platforms may not support the programmatically determination of input purposes.