Success criterion 1.3.5
Identify Input Purpose
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.
- Level AA
- Principle 1: Perceivable
- Guideline 1.3: Adaptable
In a user’s words
“Filling out forms feels like a quiz I didn't study for. But with fields that recognize me, it's more like a friendly chat.”
What each role can do
- Product manager
- Ensure all input fields in forms have clear and understandable labels.
- Designer
- Use placeholders, tooltips, or helper text to guide the user on what information is required.
- Developer
- Utilize autocomplete attributes where applicable to assist with form filling.
- Tester
- Verify that all input fields are easily identifiable and functional.
Once it is fixed
“You’ve cleared up the fog! Forms aren't a maze anymore.”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 1.3.5 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.