Test Cases Passed Passed Example 1 Open in a new tab This autocomplete attribute value only has the
required token “username”.
Passed Example 2 Open in a new tab The autocomplete attribute value of this select element has the
required token “bday-month”. The element’s form owner has autocomplete="off", which prevents the
user agent from completing it. It does not prevent the autocomplete attribute value from being
programmatically identifiable.
Passed Example 3 Open in a new tab This autocomplete attribute value only has the required token
“street-address”. Mixing upper and lower case letters is allowed for autocomplete attributes.
Passed Example 4 Open in a new tab This autocomplete attribute value list includes a work token,
allowed because it is used before email.
Passed Example 5 Open in a new tab This autocomplete attribute value list includes a section- token,
which can preface any correct autocomplete field.
Passed Example 6 Open in a new tab This autocomplete attribute value list includes section- and
billing tokens. These tokens can preface any correct autocomplete field.
Passed Example 7 Open in a new tab This autocomplete attribute value list includes all allowed types
of tokens in the correct order.
Passed Example 8 Open in a new tab This autocomplete attribute value only has the required token
“bday-day”. It remains programmatically identifiable even though it is inappropriate for the
control’s type attribute value “tel”.
Passed Example 9 Open in a new tab This autocomplete attribute value has the required token
“current-password”, followed by the optional “webauthn” token.
Failed Failed Example 1 Open in a new tab This autocomplete attribute value has an unknown term that
is not a correct autocomplete field.
Failed Example 2 Open in a new tab This autocomplete attribute value has the work token which is a
correct autocomplete field. However, work can not be used with photo.
Failed Example 3 Open in a new tab This autocomplete attribute value includes the work token before
the shipping token, instead of the other way around.
Failed Example 4 Open in a new tab This autocomplete attribute value is comma separated instead of
space using ASCII whitespace.
Failed Example 5 Open in a new tab The autocomplete attribute value is on an input element that does
not have a semantic role that is a widget role, but still participates in sequential focus
navigation because of the tabindex attribute.
Failed Example 6 Open in a new tab This autocomplete attribute does not contain any required token.
Failed Example 7 Open in a new tab This autocomplete attribute contains two of the required tokens,
but only one is allowed.
Failed Example 8 Open in a new tab This autocomplete attribute contains a work modifier but no
required token afterwards.
Failed Example 9 Open in a new tab This autocomplete attribute contains an extra token after the
allowed ones.
Failed Example 10 Open in a new tab This autocomplete attribute contains an extra token after the
allowed ones.
Inapplicable Inapplicable Example 1 Open in a new tab This autocomplete attribute value is empty
(“”).
Inapplicable Example 2 Open in a new tab This autocomplete attribute value contains only ASCII
whitespace.
Inapplicable Example 3 Open in a new tab This autocomplete attribute value is on an element that is
not visible through display:none.
Inapplicable Example 4 Open in a new tab This autocomplete attribute is on an input element that has
the disabled attribute.
Inapplicable Example 5 Open in a new tab This autocomplete attribute is on an input element that has
the aria-disabled attribute value of true.
Inapplicable Example 6 Open in a new tab This autocomplete attribute is ignored because it is on an
element with a semantic role of none. The disabled attribute is required to ensure presentational
roles conflict resolution does not cause the none role to be ignored.
Inapplicable Example 7 Open in a new tab This autocomplete attribute is inapplicable because it has
the off value.
Inapplicable Example 8 Open in a new tab This input element has a fixed value due to its type
attribute value of submit. autocomplete does not apply to Submit buttons.
Inapplicable Example 9 Open in a new tab This input element is hidden because of its type attribute
value of hidden (following standard User Agent style sheet recommendations. Knowing the transaction
amount may still be used in other fields, e.g. to suggest a card with sufficient balance; this is
not tested by this rule.