Which WCAG criterion this fails
- Does not meet 1.3.5 Identify Input Purpose (Level AA)
How to fix it on WooCommerce
Everything below is done from Appearance > Theme File Editor, or your child theme over SFTP. Take a copy of the theme before editing.
- Use the exact tokens from the HTML spec: name, given-name, family-name, email, tel, street-address, address-line1, address-line2, address-level2 (city), address-level1 (state/province), postal-code, country-name, organization.
- Custom values like autocomplete="your-email" or autocomplete="zip" are ignored — correct them.
- autocomplete="off" on an address or contact field actively harms accessibility. Remove it unless there is a real security reason.
- Shopify's own checkout already handles this; the failures are almost always in a theme contact form or a custom address block.
Where this usually lives
woocommerce/checkout/form-billing.php overrides, and form plugin field settings
Paths given for Storefront, Astra, Flatsome and other WooCommerce themes. A heavily customised theme may differ; the CSS selector in your scan report points at the exact element.
Code
<input type="email" id="Email" name="contact[email]" autocomplete="email">
<input type="tel" id="Phone" name="contact[phone]" autocomplete="tel">
<input type="text" id="Zip" name="address[zip]" autocomplete="postal-code">How to confirm it is fixed
Re-run the scan. This rule should drop out of the findings entirely. If the instance count falls but does not reach zero, the same defect exists in another template — product cards and quick-view modals are the usual second home for it.
Effort: low. Rule id: autocomplete-valid (axe-core).