Input fields have appropriate type and autocomplete attributes
Why it matters
Input fields without semantic type attributes and autocomplete tokens force users to manually re-enter information the browser already knows. For users with motor disabilities, dyslexia, or limited dexterity, autocomplete is not a convenience but a functional requirement. WCAG 2.2 SC 1.3.5 (Identify Input Purpose) is a Level AA requirement: input fields collecting personal data must use the standardized autocomplete attribute values from the HTML 5.2 spec so assistive technologies and password managers can populate them.
Severity rationale
Low because missing autocomplete attributes degrade usability for motor-impaired users without completely blocking form access — a WCAG 2.2 SC 1.3.5 Level AA compliance gap.
Remediation
Add the correct type and autocomplete attribute to every input that collects personal or contact information.
{/* Identity */}
<input type="text" autoComplete="given-name" placeholder="First name" />
<input type="text" autoComplete="family-name" placeholder="Last name" />
{/* Contact */}
<input type="email" autoComplete="email" />
<input type="tel" autoComplete="tel" />
{/* Address */}
<input type="text" autoComplete="street-address" />
<input type="text" autoComplete="postal-code" />
{/* Auth */}
<input type="password" autoComplete="current-password" />
<input type="password" autoComplete="new-password" />
Search the codebase for type="text" inputs that collect email, phone, or name data — every one is a missing semantic type. Reference the WHATWG autocomplete token list for the full set of valid values.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Accessibility WCAG Compliance Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- wcag:2.2 · 1.3.5 — Identify Input Purpose
- section-508:2018-refresh · 501.1 — Scope
Taxons
History
- 2026-04-18·v1.0.0·Initial import from accessibility-wcag·automated