Identify Input Purpose
The purpose of each input field collecting information about the user can be programmatically determined when the field serves a common input purpose and the technology used supports identifying that purpose.
In plain language
Common form fields (like name, email, or address) need to be labeled in the code in a standard way that browsers and assistive tools understand — not just visually.
Why it matters
People with cognitive disabilities may not recognize a field just from its visible label, but browsers can help by auto-filling it or showing a recognizable icon — if the field is properly identified in code. Without that, users have to figure out and type everything manually every time.
In practice
Fails this criterion
An email field is coded as a plain text input with only a visual placeholder saying "Email" — no code-level indication of its purpose, so autofill and assistive icons don't kick in.
Meets this criterion
The same field uses the proper email input type with an autocomplete="email" attribute, letting the browser recognize it, offer autofill, and show a recognizable icon.
Test it yourself
Check the site's common form fields (name, email, phone, address) using browser dev tools for an autocomplete attribute, or test whether your browser's autofill correctly recognizes them. If autofill doesn't work on standard fields, this criterion is failing.