How to fix autocomplete valid on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Identify the template file responsible for the form field. For checkout, the relevant file is typically `Magento_Checkout/web/template/form/element/input.html` or individual step templates under `Magento_Checkout/view/frontend/web/template/`.
2. Create a template override in your custom theme: copy the file to `app/design/frontend/<Vendor>/<Theme>/Magento_Checkout/web/template/` (or the relevant module path) and edit it there — never edit core files directly.
3. Locate the `<input>` element in the Knockout.js template and add the `autocomplete` binding: `autocomplete: 'given-name'` inside the `ko` bindings, or add it as a static HTML attribute.
4. For customer account forms, override `Magento_Customer/view/frontend/templates/form/` templates (e.g. `edit.phtml`, `register.phtml`) in the same way and add `autocomplete="..."` to each `<input>` tag.
5. Run `bin/magento setup:upgrade`, `bin/magento setup:static-content:deploy`, and flush the cache (`bin/magento cache:flush`) after making changes.
6. Validate on the frontend with the axe browser extension.

What is autocomplete valid?

The HTML `autocomplete` attribute tells browsers (and assistive technologies) what kind of data a form field expects — for example, a person's name, email address, shipping street address, or credit card number. WCAG Success Criterion 1.3.5 ("Identify Input Purpose") requires that any field collecting personal information carry a correct, recognised `autocomplete` value from a defined list. If the value is missing, misspelled, or used on the wrong type of field (e.g. `autocomplete="email"` on a password input), browsers and screen readers cannot reliably identify its purpose, and the autocomplete feature breaks.

For users with cognitive disabilities, motor impairments, or low vision, browser autofill is not a convenience — it is often the only practical way to complete a checkout form. An invalid or missing `autocomplete` value means autofill silently fails, forcing customers to type every field manually and dramatically increasing checkout abandonment. WCAG 1.3.5 is a Level AA requirement, which is the legal conformance target in most accessibility laws worldwide (ADA, EAA, AODA, EN 301 549); non-compliance creates real legal exposure. Fixing it also improves Google's Page Experience signals and can lift organic conversion rates, since a frictionless checkout is one of the clearest levers on revenue.

See the complete Autocomplete valid guide for every platform and the full background.