Autofill is a quiet accessibility feature. When an input carries the correct autocomplete token, browsers and password managers can fill it in automatically, which is a major help for users with motor or cognitive disabilities who would otherwise retype the same data on every form. WCAG 1.3.5 makes this a requirement for fields that collect information about the user, and this tool checks that each token you used is actually valid.
How it works
The tool parses your HTML with the browser’s DOM parser and collects each data-entry input, select and textarea. For every field it reads the autocomplete attribute and validates the value against the grammar from the HTML Living Standard:
- The special keywords
onandoffare recognised directly. - Optional prefixes are stripped in order: a
section-*group, thenshipping/billing, then a contact type such ashomeorwork. - An optional trailing
webauthntoken is removed. - The remaining single token is the field name and is checked against the permitted autofill list, for example
given-name,family-name,email,tel,street-address,postal-code,cc-numberandone-time-code.
When the field name is not in the list, the tool checks a table of common mistakes (such as phone, zip or fullname) and suggests the correct standard token.
Example
<input name="tel" type="tel" autocomplete="phone">The value phone looks reasonable but is not a real autofill token, so browsers ignore it. The correct token is tel, and the tool reports exactly that substitution.
Tips and notes
- Tokens are case-insensitive in HTML, but lower-case is the convention and is easiest to read.
- For multi-part fields, prefer the granular tokens:
address-line1,address-level2(city) andaddress-level1(state or region) rather than packing everything into one box. - Combine
shipping/billingprefixes when a page has both addresses, for exampleshipping street-addressandbilling street-address, so autofill keeps them separate. - All validation runs in your browser; the markup you paste never leaves the page.