Autofill on your forms: Crawl Audit check 119

Short answer: the autocomplete attribute tells the browser what a field is for, so it can fill in someone's name, email or phone in one tap. That's faster for everyone and essential for some disabled users. Check 119 warns when a page's form fields have no autocomplete attributes at all.

What Crawl Audit checks

• Pass: no form inputs, or at least one input with an autocomplete attribute.
• Warning: inputs, none with it.

One field with the attribute is enough to pass, so check every field that asks about the person.

What the sources say

• WCAG 1.3.5 Identify Input Purpose (level AA): "The purpose of each input field collecting information about the user can be programmatically determined".
• MDN: "Providing valid autocomplete tokens also satisfies WCAG 2.2 Success Criterion 1.3.5: Identify Input Purpose (Level AA)".
• web.dev: "If an appropriate autocomplete value is available for a form field, you should use it."

<input name="name"  autocomplete="name">
<input name="email" type="email" autocomplete="email">
<input name="phone" type="tel"   autocomplete="tel">
<input name="org"   autocomplete="organization">

Common mistakes

• autocomplete="off" on contact details. It only makes people type more.
• Made-up values. Use the standard tokens, such as given-name, street-address or postal-code, listed on MDN.

On devmarde.com

Four of the five fields in our homepage forms had autocomplete on 6 October.

Sources

• W3C, Understanding 1.3.5 Identify Input Purpose, checked 6 October 2026.
• MDN, HTML attribute: autocomplete; web.dev, Payment and address form best practices.