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 identified in the code in a standard way that browsers and assistive tools understand. A visible label alone isn't enough.
Why it matters
People with cognitive disabilities may not recognize a field from its visible label, but if the field is properly identified in the code, the browser can help by filling it in or showing a familiar icon. Without that, users have to work out and type everything by hand every time.
In practice
Fails this criterion
An email field is coded as a plain text input with only a placeholder saying "Email." Nothing in the code states its purpose, so autofill and assistive icons don't work.
Meets this criterion
The same field uses the email input type with an autocomplete="email" attribute, so the browser recognizes it, offers autofill, and can show a familiar icon.
Test it yourself
Check the site's common form fields (name, email, phone, address) in browser dev tools for an autocomplete attribute, or test whether your browser's autofill recognizes them. If autofill doesn't work on standard fields, this criterion is failing.