Forms use correct autocomplete for common inputs
What this criterion checks
This criterion maps to 1.3.5 Identify Input Purpose. A detailed plain-language description is maintained in the WebLens criteria catalogue; the WCAG sub-test breakdown below describes exactly what the agent checks and what it does not.
How it's assessed
WebLens walks each user journey, captures a screenshot at every step, and an agent reasons over that evidence. See the how WebLens works for the full pipeline and the deterministic checks layered in for accessibility.
Sub-test coverage
1.3.5 Identify Input Purpose is broken into 2 sub-tests. Coverage is honest about where the agent is reliable, where it only partially checks the requirement, and where a human reviewer is still needed.
2 partial
- Autocomplete values are correct for the fieldPartial
Our tool checks that autocomplete tokens are syntactically valid. It does not verify whether the autocomplete value semantically matches the field's actual purpose (e.g., it would not flag autocomplete="email" incorrectly used on a phone number field).
- Input fields have programmatically identified purposesPartial
Our tool validates that autocomplete attribute values present on input fields are valid tokens from the HTML specification's list of 53 input purposes. However, it does not flag input fields that collect personal user information but are missing autocomplete attributes entirely — it only validates values that are already present.
How reliable it is
This criterion is still building up testing data, so confirm its findings as you review. See Accuracy & confidence for how the confidence tags are set.