WCAG 1.3.5: Identify Input Purpose
WCAG 1.3.5 Identify Input Purpose is a level AA success criterion from WCAG 2.1. Fields that collect personal data, such as name and email, should expose their purpose with autocomplete tokens so browsers and assistive technology can fill them.
People with cognitive and motor disabilities benefit when the browser fills known fields.
How to test
Inspect checkout and account fields for autocomplete attributes such as email and name.
How to fix
Add the correct autocomplete token to each personal-data field.
Example that fails
The email field has no autocomplete attribute.
Example that passes the check
The email field uses autocomplete=email and the name field uses autocomplete=name.
Shopify
Shopify Checkout sets tokens on its own fields. Custom contact forms in the theme need autocomplete on name, email and phone.
WooCommerce
Confirm WooCommerce checkout fields keep autocomplete. Custom account fields need tokens added in the form template.
WordPress
Set autocomplete on comment and contact form fields that ask for a name or email.
Wix
In the form field settings, set the autocomplete type for name, email and phone.