# Autocomplete Tokens Nobody Sets: The One-Line Checkout Fix

Source: https://cartcomply.com/blog/2026-11-10-checkout-autocomplete-tokens-nobody-sets.html

The average US checkout shows almost fifteen form fields, and Baymard's testing says a good one needs only seven or eight. Nobody is going to cut a checkout down to eight fields tomorrow. But there is a one-line change that makes fifteen fields feel like five, and most checkouts have not made it: the autocomplete attribute. A field with the right token fills itself from the shopper's saved information. A field without it makes the shopper type, and every field they type is a field they can mistype, and a mistyped field is a failed order.

## The token is the requirement

WCAG 1.3.5, Identify Input Purpose, is a Level AA criterion, and it requires the purpose of each input collecting information about the user to be programmatically determinable. The technique the standard names is the autocomplete attribute, with the token list from the HTML specification. Email gets autocomplete email. First name gets given-name. Last name gets family-name. Phone gets tel. Street gets address-line1. Postcode gets postal-code. Card number gets cc-number. Seven tokens cover the fields shoppers type most, and the ones where a wrong guess costs a sale. The failure mode is easy to miss in testing, because a sighted tester with a password manager never sees it: the browser offers nothing, the tester types, and the test passes. A shopper on a phone, typing an address on a small keyboard with one thumb, feels every missing token. The fix is copy, not engineering: one attribute per field, and the browser does the rest.

## Wrong tokens are worse than none

A token that lies is worse than a missing one, because the browser fills the wrong data confidently. The common mistakes are easy to list. A single name field split into two inputs where the first is tagged name and the second is tagged nothing, so the browser offers the full name in the first box and nothing in the second. A company field tagged organization when the shopper is a person. A card number field tagged cc-number on a form that also asks for the number in two parts. And the worst one: autocomplete off on the whole form, usually set by a developer who thought it was a security measure. Turning autocomplete off does not make a checkout more secure. It makes it slower, and it fails 1.3.5 outright. Check the tokens the way a shopper would: open the checkout on a phone with saved information, tap each field, and see what the browser offers. If it offers nothing, the token is missing. If it offers the wrong thing, the token is wrong.

## The test that takes five minutes

The whole audit is a form, a phone, and five minutes. Load the checkout, tap the email field, and check the keyboard offers the saved email. Tap the address fields and check the browser offers the saved address. Tap the card field and check it offers the saved card. Every field that offers nothing is a token to add, and every field that offers the wrong thing is a token to fix. It is the cheapest accessibility fix in the checkout, and it is also a conversion fix, because the shopper who types less finishes more often.

Keep reading: [The Cart Close Button With No Name: Icon-Only Controls and WCAG 4.1.2](2026-11-09-cart-close-button-no-name-icon-only.md), [Quantity Steppers That Announce Themselves: Live Regions in the Cart](2026-11-07-accessible-cart-quantity-announcements.md), [Free-Shipping Progress Bars: The Threshold Message Screen Readers Never Hear](2026-11-09-free-shipping-progress-bar-screen-reader-threshold.md).

## Frequently asked questions

### What does autocomplete do on a checkout form?

It tells the browser which kind of data each field expects, so the browser can fill it from the shopper's saved information. A field with autocomplete set to email offers the saved email. A field without it offers nothing.

### Which autocomplete tokens matter most at checkout?

Email, given-name, family-name, tel, address-line1, postal-code, and cc-number. Those seven cover the fields shoppers type most, and the ones where a wrong guess costs a sale.

### Is autocomplete a WCAG requirement?

Yes. WCAG 1.3.5, Identify Input Purpose, Level AA, requires the purpose of each input collecting information about the user to be programmatically determinable, and autocomplete tokens are the technique the standard names.

### Does autocomplete help shoppers without disabilities?

Yes, and that is the point. Everyone types less and makes fewer errors. The accessibility requirement and the conversion win are the same change.