From 55a467ef9f9aa221819aba874a8ac023941bcbdf Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Sat, 24 Apr 2021 19:53:15 +0100 Subject: [PATCH 1/9] applying changes in response to Wilco's and Jym77's suggestions --- _rules/autocomplete-valid-value-73f2c2.md | 76 +++++++++++------------ 1 file changed, 38 insertions(+), 38 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index c87ee345135..d4b2d4e98f9 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -23,12 +23,13 @@ acknowledgments: This rule applies to any HTML `input`, `select` and `textarea` element with an `autocomplete` [attribute value][] that is neither empty (`""`) nor only [ASCII whitespace][], except if one of the following is true: -- **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; or +- **autofill expectation**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`; or - **disabled**: the element is a [disabled element]; or -- **fixed value**: the element is an `input` element with a `type` [attribute value][] of either `hidden`, `button`, `submit` or `reset`; or +- **fixed value**: the element is an `input` element with a `type` [attribute value][] of `hidden`, `button`, `submit` or `reset`; or +- **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; or - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]. -## Expectation 1 +## Expectation Each test target's `autocomplete` [attribute value][] is a [space separated][] list of one or more tokens that follow the [HTML specification for Autofill detail tokens][], which requires that the token list match the following in the correct order: @@ -37,19 +38,15 @@ Each test target's `autocomplete` [attribute value][] is a [space separated][] l 3. An optional token of either "home", "work", "mobile", "fax" or "pager", only if the last token is "email", "impp", "tel" or "tel-\*"; then 4. A required token from the [correct autocomplete field][]. -## Expectation 2 - -Each test target's `autocomplete` [attribute value][] has a [correct autocomplete field][] that is [appropriate][appropriate field for the form control] for that test target. - ## Assumptions The `autocomplete` attribute is used on form fields that correspond to [Input Purposes for User Interface Components](https://www.w3.org/TR/WCAG21/#input-purposes) and collect information about the user. If the `autocomplete` attribute is used to describe "custom" taxonomy, for example ``, success Criterion [1.3.5 Identify Input Purpose][sc135] may be satisfied even if this rule failed. -The `type` attribute is used correctly according to the intended purpose of `input` elements. If an incorrect `type` attribute is used for `input` elements, this rule may fail elements that satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. For example if an `input` element has a `type` of `number`, but is expecting an e-mail address. +The `aria-disabled` state is used on `input` elements which are not part of [sequential focus navigation][] and are not otherwise [operable](https://www.w3.org/TR/wai-aria-1.2/#dfn-operable). If this is not the case, this rule may be inapplicable on elements that are still operable and require a valid `autocomplete` attribute to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. -The `aria-disabled` state is used on `input` elements which are not part of [sequential focus navigation][] and are not otherwise [operable](https://www.w3.org/TR/wai-aria-1.2/#dfn-operable). If this is not the case, this rule may be inapplicable on elements that are still [operable](https://www.w3.org/TR/wai-aria-1.2/#dfn-operable) and require a valid `autocomplete` attribute to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. +The purpose of a control is programmatically identifiable even when its `autocomplete` [attribute value][] is not an [appropriate field name for the form control][]. ## Accessibility Support @@ -62,6 +59,8 @@ The `aria-disabled` state is used on `input` elements which are not part of [seq The intent of this rule is to ensure that the `autocomplete` attribute can be used to support personalization. Many users may find it easier to fill out forms if those can be styled or laid out in a way that is familiar to them. Assistive technologies can do this when a form control is marked up in such a way that its purpose can be understood. For instance, assistive technologies could add familiar icons and colors to different fields, making it easier for the user to understand what the form does. +Mainstream browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not appropriate for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. + The auto-completing feature of the `autocomplete` attribute benefits many users, but it is not required to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. Setting `autocomplete="off"` on the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) prevents the user agent from completing it, but it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. - [Understanding Success Criterion 1.3.5: Identify Input Purpose](https://www.w3.org/WAI/WCAG21/Understanding/identify-input-purpose.html) @@ -74,7 +73,7 @@ The auto-completing feature of the `autocomplete` attribute benefits many users, #### Passed Example 1 -This `autocomplete` [attribute value][] only has the required token, and is valid for an `input` element which has a default type of `text`. +This `autocomplete` [attribute value][] only has the required token "username". ```html @@ -82,7 +81,7 @@ This `autocomplete` [attribute value][] only has the required token, and is vali #### Passed Example 2 -This `autocomplete` [attribute value][] only has the required token, and is valid for a `select` element. Even though the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) has `autocomplete="off"`, thus preventing the user agent from completing it, it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. +The `autocomplete` [attribute value][] only of the `select` element has the required token "bday-month". Even though the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) has `autocomplete="off"`, thus preventing the user agent from completing it, it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. ```html
@@ -98,7 +97,7 @@ This `autocomplete` [attribute value][] only has the required token, and is vali #### Passed Example 3 -This `autocomplete` [attribute value][] only has the required token, and is valid for a `textarea` element. Mixing upper and lower case letters is allowed for `autocomplete` attributes. +This `autocomplete` [attribute value][] only has the required token "street-address". Mixing upper and lower case letters is allowed for `autocomplete` attributes. ```html @@ -106,7 +105,7 @@ This `autocomplete` [attribute value][] only has the required token, and is vali #### Passed Example 4 -This `autocomplete` [attribute value][] list includes a `work` token, allowed because it is used before `email`. The `email` token is allowed on `input` elements with a `type` [attribute value][] of `text`. +This `autocomplete` [attribute value][] list includes a `work` token, allowed because it is used before `email`. ```html @@ -114,7 +113,7 @@ This `autocomplete` [attribute value][] list includes a `work` token, allowed be #### Passed Example 5 -This `autocomplete` [attribute value][] list includes a `section-` token, which can preface any [correct autocomplete field][]. The `email` token is allowed on `input` elements with a `type` [attribute value][] of `text`. +This `autocomplete` [attribute value][] list includes a `section-` token, which can preface any [correct autocomplete field][]. ```html @@ -130,12 +129,20 @@ This `autocomplete` [attribute value][] list includes `section-` and `billing` t #### Passed Example 7 -This `autocomplete` [attribute value][] list includes all allowed types of tokens in the correct order. The `email` token is allowed on `input` elements with a `type` [attribute value][] of `text`. +This `autocomplete` [attribute value][] list includes all allowed types of tokens in the correct order. ```html ``` +#### 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 + +``` + ### Failed #### Failed Example 1 @@ -148,7 +155,7 @@ This `autocomplete` [attribute value][] has an unknown term that is not a [corre #### Failed Example 2 -This `autocomplete` [attribute value][] has the `work` token on a [correct autocomplete field][], however `work` can not be used with `photo`. +This `autocomplete` [attribute value][] has the `work` token which is a [correct autocomplete field][]. However, `work` can not be used with `photo`. ```html @@ -190,21 +197,13 @@ The `autocomplete` attribute value is on an `input` element that does not have a #### Inapplicable Example 1 -This `button` element does not support `autocomplete` attributes. - -```html - -``` - -#### Inapplicable Example 2 - This `autocomplete` [attribute value][] is empty (""). ```html ``` -#### Inapplicable Example 3 +#### Inapplicable Example 2 This `autocomplete` [attribute value][] contains only [ASCII whitespace][]. @@ -212,7 +211,7 @@ This `autocomplete` [attribute value][] contains only [ASCII whitespace][]. ``` -#### Inapplicable Example 4 +#### Inapplicable Example 3 This `autocomplete` [attribute value][] is on an element that is not [visible][] through `display:none`. @@ -220,15 +219,7 @@ This `autocomplete` [attribute value][] is on an element that is not [visible][] ``` -#### Inapplicable Example 5 - -This `autocomplete` attribute is on an `input` element with a `type` [attribute value][] that does not support autocomplete. - -```html - -``` - -#### Inapplicable Example 6 +#### Inapplicable Example 4 This `autocomplete` attribute is on an `input` element that has the `disabled` attribute. @@ -236,7 +227,7 @@ This `autocomplete` attribute is on an `input` element that has the `disabled` a ``` -#### Inapplicable Example 7 +#### Inapplicable Example 5 This `autocomplete` attribute is on an `input` element that has the `aria-disabled` [attribute value][] of `true`. @@ -244,7 +235,7 @@ This `autocomplete` attribute is on an `input` element that has the `aria-disabl ``` -#### Inapplicable Example 8 +#### Inapplicable Example 6 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. @@ -252,9 +243,18 @@ This `autocomplete` attribute is ignored because it is on an element with a [sem ``` +#### Inapplicable Example 7 + +This `autocomplete` attribute is inapplicable because it has the `off` value. + +```html + +``` + [ascii whitespace]: https://infra.spec.whatwg.org/#ascii-whitespace 'HTML ASCII whitespace 2020/08/12' +[ascii case-insensitive]: https://infra.spec.whatwg.org/#ascii-case-insensitive 'definition of ASCII case-insensitive' [attribute value]: #attribute-value 'Definition of Attribute Value' -[appropriate field for the form control]: #appropriate-field-for-the-form-control 'Definition of Appropriate field for the form control' +[appropriate field name for the form control]: #appropriate-field-for-the-form-control 'Definition of Appropriate field for the form control' [correct autocomplete field]: #correct-autocomplete-field 'Definition of Correct autocomplete field' [disabled element]: #disabled-element 'Definition of Disabled Element' [html specification for autofill detail tokens]: https://html.spec.whatwg.org/#autofill-detail-tokens 'HTML Autofill Detail, 2020/08/12' From 593711609bb81f00275397b5cd78312b08313a94 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Tue, 27 Apr 2021 13:26:36 +0100 Subject: [PATCH 2/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Wilco Fiers --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index d4b2d4e98f9..2abbdf7df6f 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -23,7 +23,7 @@ acknowledgments: This rule applies to any HTML `input`, `select` and `textarea` element with an `autocomplete` [attribute value][] that is neither empty (`""`) nor only [ASCII whitespace][], except if one of the following is true: -- **autofill expectation**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`; or +- **toggle**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`; or - **disabled**: the element is a [disabled element]; or - **fixed value**: the element is an `input` element with a `type` [attribute value][] of `hidden`, `button`, `submit` or `reset`; or - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; or From f6e06b30142bbc71e9264c002e600ecdfee95a61 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Tue, 27 Apr 2021 13:27:16 +0100 Subject: [PATCH 3/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Wilco Fiers --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 2abbdf7df6f..eeaa8bcf45f 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -44,7 +44,7 @@ The `autocomplete` attribute is used on form fields that correspond to [Input Pu If the `autocomplete` attribute is used to describe "custom" taxonomy, for example ``, success Criterion [1.3.5 Identify Input Purpose][sc135] may be satisfied even if this rule failed. -The `aria-disabled` state is used on `input` elements which are not part of [sequential focus navigation][] and are not otherwise [operable](https://www.w3.org/TR/wai-aria-1.2/#dfn-operable). If this is not the case, this rule may be inapplicable on elements that are still operable and require a valid `autocomplete` attribute to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. +The `aria-disabled` state is used on `input` elements which are not part of [sequential focus navigation][] and are not otherwise [operable](https://www.w3.org/TR/wai-aria-1.2/#dfn-operable). If this is not the case, this rule may be inapplicable on elements that are still operable and require a valid `autocomplete` attribute to satisfy success criterion [1.3.5 Identify Input Purpose][sc135]. The purpose of a control is programmatically identifiable even when its `autocomplete` [attribute value][] is not an [appropriate field name for the form control][]. From a28ea11c6f7b533ae3770dd37aada31fbba029ca Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Tue, 27 Apr 2021 13:27:53 +0100 Subject: [PATCH 4/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Wilco Fiers --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index eeaa8bcf45f..783d1158aa2 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -59,7 +59,7 @@ The purpose of a control is programmatically identifiable even when its `autocom The intent of this rule is to ensure that the `autocomplete` attribute can be used to support personalization. Many users may find it easier to fill out forms if those can be styled or laid out in a way that is familiar to them. Assistive technologies can do this when a form control is marked up in such a way that its purpose can be understood. For instance, assistive technologies could add familiar icons and colors to different fields, making it easier for the user to understand what the form does. -Mainstream browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not appropriate for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. +Many browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not appropriate for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. The auto-completing feature of the `autocomplete` attribute benefits many users, but it is not required to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. Setting `autocomplete="off"` on the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) prevents the user agent from completing it, but it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. From 54931246556e5feaab82d3df761a216f1af5c278 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Tue, 27 Apr 2021 13:28:37 +0100 Subject: [PATCH 5/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Wilco Fiers --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 783d1158aa2..8f7e0bdcec9 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -81,7 +81,7 @@ This `autocomplete` [attribute value][] only has the required token "username". #### Passed Example 2 -The `autocomplete` [attribute value][] only of the `select` element has the required token "bday-month". Even though the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) has `autocomplete="off"`, thus preventing the user agent from completing it, it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. +The `autocomplete` [attribute value][] of the `select` element has the required token "bday-month". Even though the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) has `autocomplete="off"`. This prevents the user agent from completing it, but does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. ```html From 397c22b6f1e4d1ce1033829702aeff564c26a2ac Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Sat, 8 May 2021 23:25:10 +0100 Subject: [PATCH 6/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Jean-Yves Moyen --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 8f7e0bdcec9..f45b0896c02 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -59,7 +59,7 @@ The purpose of a control is programmatically identifiable even when its `autocom The intent of this rule is to ensure that the `autocomplete` attribute can be used to support personalization. Many users may find it easier to fill out forms if those can be styled or laid out in a way that is familiar to them. Assistive technologies can do this when a form control is marked up in such a way that its purpose can be understood. For instance, assistive technologies could add familiar icons and colors to different fields, making it easier for the user to understand what the form does. -Many browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not appropriate for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. +Many browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not [appropriate][] for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. The auto-completing feature of the `autocomplete` attribute benefits many users, but it is not required to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. Setting `autocomplete="off"` on the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) prevents the user agent from completing it, but it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. From ab1774cb711466f47f6bfb63c672c40badf51260 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Sat, 8 May 2021 23:26:05 +0100 Subject: [PATCH 7/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Jean-Yves Moyen --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index f45b0896c02..b2cedecfbc4 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -81,7 +81,7 @@ This `autocomplete` [attribute value][] only has the required token "username". #### Passed Example 2 -The `autocomplete` [attribute value][] of the `select` element has the required token "bday-month". Even though the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) has `autocomplete="off"`. This prevents the user agent from completing it, but does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. +The `autocomplete` [attribute value][] of this `select` element has the required token "bday-month". Even though the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) has `autocomplete="off"`. This prevents the user agent from completing it, but does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. ```html From afdee15de29cd491ebd1e376b3b145e0802e4b6a Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Sat, 8 May 2021 23:34:37 +0100 Subject: [PATCH 8/9] Fixing a link --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index b2cedecfbc4..010ca7e5309 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -59,7 +59,7 @@ The purpose of a control is programmatically identifiable even when its `autocom The intent of this rule is to ensure that the `autocomplete` attribute can be used to support personalization. Many users may find it easier to fill out forms if those can be styled or laid out in a way that is familiar to them. Assistive technologies can do this when a form control is marked up in such a way that its purpose can be understood. For instance, assistive technologies could add familiar icons and colors to different fields, making it easier for the user to understand what the form does. -Many browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not [appropriate][] for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. +Many browsers provide auto-filling suggestions even when the control's `type` [attribute value][] is not [appropriate][appropriate field name for the form control] for its `autocomplete` [attribute value][]. The same happens when the `autocomplete` property is queried. However, the `autocomplete` property is not programmatically identifiable if the requirements for the optional tokens are not met. The auto-completing feature of the `autocomplete` attribute benefits many users, but it is not required to satisfy success Criterion [1.3.5 Identify Input Purpose][sc135]. Setting `autocomplete="off"` on the element's [form owner](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-owner) prevents the user agent from completing it, but it does not prevent the `autocomplete` [attribute value][] from being programmatically identifiable. From dfaea5eaaea352506e223b39036f955004deac63 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Wed, 2 Jun 2021 23:03:41 +0100 Subject: [PATCH 9/9] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Carlos Duarte --- _rules/autocomplete-valid-value-73f2c2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 010ca7e5309..469c9978c1e 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -23,7 +23,7 @@ acknowledgments: This rule applies to any HTML `input`, `select` and `textarea` element with an `autocomplete` [attribute value][] that is neither empty (`""`) nor only [ASCII whitespace][], except if one of the following is true: -- **toggle**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`; or +- **toggle**: the `autocomplete` attribute consists of a single token that is an [ASCII case-insensitive][] match for the string `off` or the string `on`; or - **disabled**: the element is a [disabled element]; or - **fixed value**: the element is an `input` element with a `type` [attribute value][] of `hidden`, `button`, `submit` or `reset`; or - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; or