Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[73f2c2] Autocomplete invalid - Accessibility note clarifies HTML spec's disallowed autocomplete values for specific form controls #2161

Merged
merged 5 commits into from
Jun 10, 2024
Merged

[73f2c2] Autocomplete invalid - Accessibility note clarifies HTML spec's disallowed autocomplete values for specific form controls #2161

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
393e8d5
solving discussion in 1967
giacomo-petri Feb 9, 2024
450f463
Merge branch 'develop' into giacomo-petri-1.3.5-autocomplete-attr-val…
Jym77 Feb 15, 2024
b721e65
Update autocomplete-valid-value-73f2c2.md
giacomo-petri Mar 4, 2024
880e670
Merge branch 'develop' into giacomo-petri-1.3.5-autocomplete-attr-val…
Jym77 Apr 18, 2024
056d0ea
Merge branch 'develop' into giacomo-petri-1.3.5-autocomplete-attr-val…
Jym77 Jun 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions _rules/autocomplete-valid-value-73f2c2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,7 @@ The purpose of a control is programmatically identifiable even when its `autocom
- Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have a [semantic role][] of `none` and fail this rule with some technology but users of other technologies would not experience any accessibility issue.
- Some user agents treat the value of the `aria-disabled` attribute as case-sensitive.
- In some user agents, querying the value of the `autocomplete` property returns an empty string ("") even when the attribute was set according to the rule's expectations. It affects assistive technologies which rely on this property to personalize input fields collecting information about the user.
- Authors may assign inappropriate `autocomplete` attribute values. Moreover, HTML specifications restrict certain `autocomplete` attribute values to specific form controls. Mismatches between `autocomplete` attribute values and form control types may or may not lead to a failure of [Success Criterion 1.3.5 Identify Input Purpose](https://www.w3.org/TR/WCAG22/#identify-input-purpose). However, this rule focuses exclusively on validating valid `autocomplete` attribute values, disregarding their contextual appropriateness.

## Background

Expand Down Expand Up @@ -147,14 +148,6 @@ This `autocomplete` [attribute value][] list includes all allowed types of token

#### Passed Example 8

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".

```html
<label>Birthday day<input name="bdayday" type="tel" autocomplete="bday-day"/></label>
```

#### Passed Example 9

This `autocomplete` [attribute value][] has the required token "current-password", followed by the optional "webauthn" token.

```html
Expand Down
Loading