In plain language
Fields that collect the user's own details (name, email, phone, address, card) must carry the correct autocomplete attribute.
Who it affects
People with motor or cognitive disabilities who rely on browser autofill for personal data.
How to check
Inspect personal-data fields for a valid, correct autocomplete token; test that browser autofill actually fills them. Worked example — A news outlet's article page: inspect a custom-built 'smart field' component in DevTools: check whether the rendered input still carries the correct native autocomplete attribute, or whether the framework stripped it.
Common misconception
Setting the input type (like type="email") is not the same as setting autocomplete. Browsers and password managers rely specifically on the autocomplete attribute to know what a field collects. Real example: on a nonprofit's donation form, the autocomplete attribute has an invalid or wrong value (e.g., 'given-name' on a surname field) — browsers and tools can't identify or autofill the field.