WCAG 1.3.5: Identify Input Purpose
Level AAQuick answer: Common user-data fields should expose their purpose programmatically so browsers and assistive tech can help fill them accurately.
What This Means
On ecommerce sites, Identify Input Purpose usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like checkout fields use generic names like field1 and field2 instead of autocomplete tokens. or account signup collects shipping address but omits autocomplete attributes., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Checkout fields use generic names like field1 and field2 instead of autocomplete tokens.
- Account signup collects shipping address but omits autocomplete attributes.
- Gift recipient forms reuse one text input for first and last name with no purpose metadata.
- Payment-support pages ask for phone and email without semantic input purpose.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Add valid autocomplete tokens like email, given-name, address-line1, and postal-code.
- Keep each field focused on one purpose instead of combining multiple pieces of data.
- Review custom checkout apps that replace native inputs and often drop semantic metadata.
- Map CMS or form-builder components to the correct HTML input types and autocomplete values.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<input name="customerEmail">
<!-- After -->
<input type="email" name="customerEmail" autocomplete="email">FAQ
What is WCAG 1.3.5?
Common user-data fields should expose their purpose programmatically so browsers and assistive tech can help fill them accurately.
How does WCAG 1.3.5 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with checkout fields use generic names like field1 and field2 instead of autocomplete tokens. and account signup collects shipping address but omits autocomplete attributes. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 1.3.5 violations?
Start by auditing the live storefront, then Add valid autocomplete tokens like email, given-name, address-line1, and postal-code.; Keep each field focused on one purpose instead of combining multiple pieces of data.; Review custom checkout apps that replace native inputs and often drop semantic metadata.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 1.3.5 → Free ADA Compliance Scan