A11Y-021
Personal-data fields use an invalid autocomplete value
LowDefault severity · Accessibility · Accessibility (WCAG 2.2 AA)
Last reviewed
What it checks
autocomplete values on email, phone, name and address fields against the HTML autofill tokens.
Why it matters
Browsers and assistive tools cannot fill or identify the field, which WCAG 1.3.5 requires for personal data and which slows down everyone.
Recommended fix
Use the standard token, for example autocomplete="email", "tel" or "given-name".
How to verify
Run axe and confirm no autocomplete-valid issues.
Example fix prompt
Generic prompt (your report adds the evidence)
Please fix this production issue in my app.
Issue A11Y-021: Personal-data fields use an invalid autocomplete value
Site: https://your-app.example
First confirm the issue in the code or live config. If it is not present, say so and change nothing.
Task: Replace the invalid autocomplete values in the evidence with the standard HTML tokens for each field (email, tel, given-name, family-name, street-address, postal-code …).
Constraints: make the smallest change that fixes this, keep the current design and behaviour, never paste secret values into code or chat, and tell me which files you changed.
Done when: Run axe and confirm no autocomplete-valid issues.