a11y/autocomplete-valid

Dlaczego

Browsers and assistive technology fill and label fields from the autocomplete value. An invented value (autocomplete="e-mail", "nope") is ignored, so people with motor or memory impairments must type everything again, and the field's purpose is not exposed.

Poprawka

Use a field name from the standard (name, given-name, family-name, email, tel, street-address, postal-code, country-name, bday, username, current-password, new-password, one-time-code, cc-number…), optionally preceded by section-*, shipping or billing, and for contact fields home, work or mobile. Use off only where autofill would be wrong, never to stop password managers.

Przykłady

<!-- bad -->
<input id="mail" type="email" autocomplete="e-mail">
<!-- good -->
<input id="mail" type="email" autocomplete="email">
<input id="ship-zip" autocomplete="shipping postal-code">

Źródła

• WCAG 2.2, Understanding SC 1.3.5 Identify Input Purpose
• WHATWG HTML, autofilling form controls (the autocomplete attribute)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain a11y/autocomplete-valid