WCAG 2.1 · Level AA · Perceivable
1.3.5 Identify Input Purpose
Manual verification
How to validate 1.3.5 by hand
Review form fields that ask for personal information about the user and check whether their purpose is programmatically identified.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Identify fields requesting common personal data such as name, email, telephone, address, or payment information.
- Inspect the field’s autocomplete purpose token and compare it with the data being requested.
- Test whether the browser or assistive technology can identify and offer the appropriate autofill value without changing the field’s visible label.
Evidence to record
Record the field label, requested data, autocomplete token, and any mismatch between the field’s purpose and its programmatic value.
Scope and exceptions
This criterion applies to fields collecting information about the user for which a defined purpose exists. Do not infer a failure for unrelated data or fields that do not meet the criterion’s scope.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.