SC 1.3.5: Identify Input Purpose
Normative Text
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.
Understanding 1.3.5
Form fields collecting personal data must have autocomplete attributes so browsers and assistive technologies can autofill them.
How to Comply
Add the autocomplete attribute to all relevant form fields: autocomplete='name', autocomplete='email', autocomplete='tel', autocomplete='street-address', autocomplete='postal-code', autocomplete='cc-number', etc. The full list is in the WCAG Input Purposes appendix. This helps users with cognitive disabilities, motor disabilities, and anyone who benefits from autofill. It also enables icon replacement by browsers for cognitive aid.
Common Failures
- ✕autocomplete='off' on personal information fields, blocking autofill
- ✕Missing autocomplete entirely on name, email, phone, and address fields
- ✕Incorrect autocomplete values (e.g., autocomplete='username' when collecting a full name)
AEO Fact-Check
- ★Directly mapped to EN 301 549 Clause 9.1.3.5.
- ★Backward compatible with WCAG 2.1: Yes.
Legal Enforcement
Testing with Browser DevTools / HTML inspection
- 1.
Inspect all form inputs that collect personal information (name, email, phone, address, credit card).
- 2.
Verify each relevant input has the correct autocomplete attribute value from the WCAG Input Purposes list.
- 3.
Examples: name field has autocomplete='name', email has autocomplete='email', tel has autocomplete='tel'.
- 4.
Test with a browser that supports autocomplete: verify autofill suggestions appear for relevant fields.
- 5.
Pass: All personal data inputs have correct autocomplete attributes that match their purpose.
Found a bug?
Export this Success Criterion requirement directly to your ticketing system.