autocomplete-valid
autocomplete attribute must be a valid autofill value
Checks that a non-empty autocomplete attribute is "on"/"off" or a well-formed autofill detail token list.
Applies to. Applies to form controls (input, select, textarea) with a non-empty autocomplete attribute. Disabled controls (the disabled attribute, including a control disabled by a disabled fieldset ancestor, or aria-disabled="true") and input types with a fixed value are exempt, as in ACT 73f2c2.
Expectation. The value is "on"/"off" alone, or a well-formed autofill detail token list: an optional "section-*" token, then an optional "shipping"/"billing" token, then an optional contact-modality token (home/work/mobile/fax/pager), then exactly one recognized field-name token (name, email, street-address, cc-number, tel, ...), optionally followed by "webauthn". A malformed value means the field is not reliably identified for assistive technology that relies on autocomplete to describe the expected input purpose.
What a finding reports.
value: the autocomplete value as written, trimmed.
These data.details fields help to read and reproduce a finding. Apart from reasonCode and the few fields Output schema names as stable, they are not a stable contract: a field may be renamed or dropped in a minor release, so don’t build on them.
Examples
<input autocomplete="email">
"email" is a recognized autofill field-name token.
<input autocomplete="emial">
"emial" is a typo, not a recognized autofill token.