From 1f735b04ef7878394112c2d294ceb6b6ebc29024 Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Mon, 18 Jan 2021 23:10:32 +0000 Subject: [PATCH 01/15] Editorial changes in response to TF feedback --- _rules/autocomplete-valid-value-73f2c2.md | 23 +++++++---------------- 1 file changed, 7 insertions(+), 16 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index b47b6f6348f..746b79d171c 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -24,7 +24,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: - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; or -- **disabled**: the element has an `aria-disabled` [attribute value][] of `true`; or +- **disabled**: the element has the `disabled` attribute or the `aria-disabled` [attribute value][] of `true`; or - **fixed value**: the element is an `input` element with a `type` [attribute value][] of either `hidden`, `button`, `submit` or `reset`; or - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]. @@ -45,8 +45,6 @@ Each test target's `autocomplete` [attribute value][] has a [correct autocomplet 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` field is used to describe "custom" taxonomy, rather than that described in the list of `input` purposes, or the form fields do not collect information about the user, 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](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]. @@ -86,7 +84,8 @@ This `autocomplete` [attribute value][] only has the required token, and is vali ```html
- @@ -98,7 +97,7 @@ This `autocomplete` [attribute value][] only has the required token, and is vali 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. ```html - + ``` #### Passed Example 4 @@ -114,7 +113,7 @@ This `autocomplete` [attribute value][] list includes a `work` token, allowed be 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`. ```html - + ``` #### Passed Example 6 @@ -122,7 +121,7 @@ This `autocomplete` [attribute value][] list includes a `section-` token, which This `autocomplete` [attribute value][] list includes `section-` and `billing` tokens. These tokens can preface any [correct autocomplete field][]. ```html - + ``` #### Passed Example 7 @@ -130,15 +129,7 @@ This `autocomplete` [attribute value][] list includes `section-` and `billing` t 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`. ```html - -``` - -#### Passed Example 8 - -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. - -```html - + ``` ### Failed From 07bbefebd33f178bf15f1f39db7b6911da4dd705 Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Wed, 17 Feb 2021 17:14:22 +0000 Subject: [PATCH 02/15] suggestions from #1540 and #1541 --- _rules/autocomplete-valid-value-73f2c2.md | 24 ++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index c87ee345135..62f35635aa4 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -26,7 +26,8 @@ This rule applies to any HTML `input`, `select` and `textarea` element with an ` - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; 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 -- **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]. +- **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][] +- the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle). ## Expectation 1 @@ -39,15 +40,20 @@ Each test target's `autocomplete` [attribute value][] is a [space separated][] l ## 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. +Each test target's `autocomplete` [attribute value][] has a [correct autocomplete field][] that is [appropriate][appropriate field for the form control] for that its control group. It means that, for example, an `input` element with `autocomplete="new-password"` must have the `type` attribute with one of the following values: + +- `hidden` (in this case the test target is inapplicable), +- `text`, +- `search`, +- `password`. ## 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. +Controls with the `autocomplete` attribute that wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle) (e.g. ``) are assumed not to collect information about the user or do not correspond to [Input Purposes for User Interface Components](https://www.w3.org/TR/WCAG21/#input-purposes); therefore, they are inapplicable. -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. +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](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]. @@ -148,7 +154,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 on a [correct autocomplete field][], however, `work` can not be used with `photo`. ```html @@ -252,6 +258,14 @@ This `autocomplete` attribute is ignored because it is on an element with a [sem ``` +#### Inapplicable Example 9 + +This `autocomplete` attribute does not collect information about the user + +```html + +``` + [ascii whitespace]: https://infra.spec.whatwg.org/#ascii-whitespace 'HTML ASCII whitespace 2020/08/12' [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' From 561e9b7e0cd727273841f3c5f8cfe8269127bc58 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Thu, 18 Feb 2021 20:53:37 +0000 Subject: [PATCH 03/15] Update _rules/autocomplete-valid-value-73f2c2.md Co-authored-by: Jean-Yves Moyen --- _rules/autocomplete-valid-value-73f2c2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 62f35635aa4..d9c0ecfa721 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -26,8 +26,8 @@ This rule applies to any HTML `input`, `select` and `textarea` element with an ` - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; 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 -- **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][] -- the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle). +- **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]; or +- **autofill expectation** the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle). ## Expectation 1 From 90fcb2fbe6b5120de51df32b316eb94c276d6a08 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Thu, 18 Feb 2021 22:48:17 +0000 Subject: [PATCH 04/15] Per @Jym77 suggestions --- _rules/autocomplete-valid-value-73f2c2.md | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index d9c0ecfa721..5113fb07896 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -27,7 +27,7 @@ This rule applies to any HTML `input`, `select` and `textarea` element with an ` - **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 - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]; or -- **autofill expectation** the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle). +- **autofill expectation** the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle) that does not consist of a single token that is ASCII case-insensitive match for string `off` or string `on`. ## Expectation 1 @@ -40,19 +40,12 @@ Each test target's `autocomplete` [attribute value][] is a [space separated][] l ## 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 its control group. It means that, for example, an `input` element with `autocomplete="new-password"` must have the `type` attribute with one of the following values: - -- `hidden` (in this case the test target is inapplicable), -- `text`, -- `search`, -- `password`. +Each test target's `autocomplete` [attribute value][] has a [correct autocomplete field][]. The autocomplete field is [appropriate][appropriate field for the form control], meaning that it can be used with the control's `type` attribute. ## 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. -Controls with the `autocomplete` attribute that wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle) (e.g. ``) are assumed not to collect information about the user or do not correspond to [Input Purposes for User Interface Components](https://www.w3.org/TR/WCAG21/#input-purposes); therefore, they are inapplicable. - 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](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]. @@ -260,13 +253,14 @@ This `autocomplete` attribute is ignored because it is on an element with a [sem #### Inapplicable Example 9 -This `autocomplete` attribute does not collect information about the user +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' [correct autocomplete field]: #correct-autocomplete-field 'Definition of Correct autocomplete field' From fc8bb3e8405b02e9ff85afb93565eac7238ae5eb Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Thu, 18 Feb 2021 22:59:44 +0000 Subject: [PATCH 05/15] ASCII case-insensitive error fix --- _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 5113fb07896..7851a65fb36 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -27,7 +27,7 @@ This rule applies to any HTML `input`, `select` and `textarea` element with an ` - **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 - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]; or -- **autofill expectation** the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle) that does not consist of a single token that is ASCII case-insensitive match for string `off` or string `on`. +- **autofill expectation** the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle) that does not consist of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`. ## Expectation 1 From b48ae5dc39dca3146bd3cd1759e0821a94770950 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Mon, 22 Mar 2021 09:05:32 +0000 Subject: [PATCH 06/15] 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 7851a65fb36..3532d228340 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -27,7 +27,7 @@ This rule applies to any HTML `input`, `select` and `textarea` element with an ` - **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 - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]; or -- **autofill expectation** the `autocomplete` attribute wears the [autofill expectation mantle](https://html.spec.whatwg.org/#autofill-expectation-mantle) that does not consist of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`. +- **autofill expectation**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`. ## Expectation 1 From a18822e47ab7275f11b0ec71b578c93a0b6ed523 Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Mon, 22 Mar 2021 09:22:54 +0000 Subject: [PATCH 07/15] changing order for better readability- J-Y M suggestion --- _rules/autocomplete-valid-value-73f2c2.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 3532d228340..9e97b3f6e87 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -23,11 +23,11 @@ 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 - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; 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 -- **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]; or -- **autofill expectation**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`. +- **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]. ## Expectation 1 @@ -40,7 +40,7 @@ Each test target's `autocomplete` [attribute value][] is a [space separated][] l ## Expectation 2 -Each test target's `autocomplete` [attribute value][] has a [correct autocomplete field][]. The autocomplete field is [appropriate][appropriate field for the form control], meaning that it can be used with the control's `type` attribute. +Each test target's `autocomplete` [attribute value][] has a [correct autocomplete field][]. The autocomplete field is [appropriate][appropriate field for the form control], meaning that it can be used with the control's `type` attribute. ## Assumptions From df414d6fdec64483b9da9e266660f77898011ea7 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Fri, 16 Apr 2021 22:27:00 +0100 Subject: [PATCH 08/15] refactoring type --- _rules/autocomplete-valid-value-73f2c2.md | 52 ++++++++--------------- 1 file changed, 17 insertions(+), 35 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 9e97b3f6e87..cb3a77a34a8 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -26,7 +26,7 @@ This rule applies to any HTML `input`, `select` and `textarea` element with an ` - **autofill expectation**: the `autocomplete` attribute consists of a single token that is [ASCII case-insensitive][] match for string `off` or string `on`; or - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; 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 - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]. ## Expectation 1 @@ -38,19 +38,17 @@ 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][]. The autocomplete field is [appropriate][appropriate field for the form control], meaning that it can be used with the control's `type` attribute. - ## 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 `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 `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]. -## Accessibility Support +Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognise the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value]. + +## Accessibility Support - While `autocomplete` is a promising technique for supporting personalization in HTML, support for this in assistive technologies is fairly limited. - 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. @@ -81,7 +79,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. 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 @@ -97,7 +95,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. Mixing upper and lower case letters is allowed for `autocomplete` attributes. ```html @@ -105,7 +103,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 @@ -113,7 +111,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 @@ -129,7 +127,7 @@ 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 @@ -189,21 +187,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][]. @@ -211,7 +201,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`. @@ -219,15 +209,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. @@ -235,7 +217,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`. @@ -243,7 +225,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. @@ -251,7 +233,7 @@ This `autocomplete` attribute is ignored because it is on an element with a [sem ``` -#### Inapplicable Example 9 +#### Inapplicable Example 7 This `autocomplete` attribute is inapplicable because it has the `off` value. @@ -262,7 +244,7 @@ This `autocomplete` attribute is inapplicable because it has the `off` value. [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 149a7aba327908330cd295988de8fabf45748273 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Fri, 16 Apr 2021 23:05:30 +0100 Subject: [PATCH 09/15] spelling error recognize, not recognise --- _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 cb3a77a34a8..7407353be25 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -46,7 +46,7 @@ If the `autocomplete` attribute is used to describe "custom" taxonomy, for examp 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]. -Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognise the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value]. +Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognize the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value]. ## Accessibility Support From 38fe055b65f8d6d40323a6974168b65e4609fbd6 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Mon, 19 Apr 2021 11:42:51 +0100 Subject: [PATCH 10/15] 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 7407353be25..322a46e88a7 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -48,7 +48,7 @@ The `aria-disabled` state is used on `input` elements which are not part of [seq Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognize the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value]. -## Accessibility Support +## Accessibility Support - While `autocomplete` is a promising technique for supporting personalization in HTML, support for this in assistive technologies is fairly limited. - 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. From bb7d4bf1ed153fcabaaa36b8430ada14e2605a18 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Mon, 19 Apr 2021 14:48:46 +0100 Subject: [PATCH 11/15] Update embedded-image.md --- pages/glossary/embedded-image.md | 1 + 1 file changed, 1 insertion(+) diff --git a/pages/glossary/embedded-image.md b/pages/glossary/embedded-image.md index 30e97088f3f..288fced5921 100755 --- a/pages/glossary/embedded-image.md +++ b/pages/glossary/embedded-image.md @@ -15,6 +15,7 @@ An element presents an _embedded image_ when any of the following is true: - the element is an `svg` element having one or more `image` [descendants][] with a non-empty `href` [attribute value][]; or - the element has a [computed][] [`background-image`][background-image] CSS property with at least one [`image`][css-image] that is a [url reference][url-reference]. + [attribute value]: #attribute-value 'Definition of Attribute Value' [background-image]: https://drafts.csswg.org/css-backgrounds-3/#background-image [computed]: https://www.w3.org/TR/css-cascade-4/#computed 'CSS Cascading and Inheritance Level 4 (Working draft) - Computed Values' From 7855e22a818a009993461812da387a28976b1db4 Mon Sep 17 00:00:00 2001 From: Aron Janecki Date: Mon, 19 Apr 2021 14:50:10 +0100 Subject: [PATCH 12/15] Update rendered-image-resource.md From ffd3f0abe591d6a23d3b9513a4966c6c6d89b741 Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Mon, 19 Apr 2021 15:40:18 +0100 Subject: [PATCH 13/15] As per Wilco suggesstions --- _rules/autocomplete-valid-value-73f2c2.md | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index 322a46e88a7..3c5bd720ff6 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -46,7 +46,7 @@ If the `autocomplete` attribute is used to describe "custom" taxonomy, for examp 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]. -Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognize the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value]. +Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognize the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value][]. ## Accessibility Support @@ -71,7 +71,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 @@ -79,7 +79,7 @@ This `autocomplete` [attribute value][] only has the required token, and is vali #### Passed Example 2 -The `autocomplete` [attribute value][] only of the `select` element has the required token. 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 @@ -95,7 +95,7 @@ The `autocomplete` [attribute value][] only of the `select` element has the requ #### Passed Example 3 -This `autocomplete` [attribute value][] only has the required token. 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 @@ -133,6 +133,14 @@ 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 + +``` + ### Failed #### Failed Example 1 @@ -145,7 +153,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 From a8fc7fda635e2857142ee6d5ad8976e885083a09 Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Sat, 24 Apr 2021 10:47:59 +0100 Subject: [PATCH 14/15] trying remove additional files --- ...aria-state-or-property-permitted-5c01ea.md | 4 +- _rules/autocomplete-valid-value-73f2c2.md | 70 +++++++++---------- _rules/block-collapsible-3e12e1.md | 16 ++--- _rules/bypass-blocks-cf77f2.md | 4 +- ...eadings-for-non-repeated-content-047fe0.md | 6 +- ...strument-to-non-repeated-content-ye5d6e.md | 4 +- _rules/menuitem-non-empty-name-m6b1q3.md | 4 +- _rules/video-alternative-for-visual-c5a4ea.md | 2 +- 8 files changed, 54 insertions(+), 56 deletions(-) diff --git a/_rules/aria-state-or-property-permitted-5c01ea.md b/_rules/aria-state-or-property-permitted-5c01ea.md index 4d906f8d5b5..06223184130 100755 --- a/_rules/aria-state-or-property-permitted-5c01ea.md +++ b/_rules/aria-state-or-property-permitted-5c01ea.md @@ -83,7 +83,7 @@ The `aria-busy` [state][] is a [global][] [state][] that is [supported][] by all #### Passed Example 4 -The `aria-label` [state][] is a [global][] [state][] and thus [inherited][] for all [semantic role][]. +The `aria-label` [property][] is a [global][] [property][] and thus [inherited][] for all [semantic role][]. ```html
✓
@@ -123,7 +123,7 @@ The `aria-controls` [property][] is [required][] for the [semantic role][] `comb #### Passed Example 9 -The `aria-label` [state][] is [global][] and thus [inherited][] for all [semantic role][], including the ones from the [WAI-ARIA Graphics Module](https://www.w3.org/TR/graphics-aria-1.0). This rule is also applicable to SVG elements. +The `aria-label` [property][] is [global][] and thus [inherited][] for all [semantic role][], including the ones from the [WAI-ARIA Graphics Module](https://www.w3.org/TR/graphics-aria-1.0). This rule is also applicable to SVG elements. ```html diff --git a/_rules/autocomplete-valid-value-73f2c2.md b/_rules/autocomplete-valid-value-73f2c2.md index c87ee345135..3c5bd720ff6 100755 --- a/_rules/autocomplete-valid-value-73f2c2.md +++ b/_rules/autocomplete-valid-value-73f2c2.md @@ -23,9 +23,10 @@ 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 - **hidden**: the element is not [visible][], and not [included in the accessibility tree][]; 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 - **static**: the element is not part of [sequential focus navigation][] and has a [semantic role][] that is not a [widget role][]. ## Expectation 1 @@ -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]. +Mainstream user agents tend to provide autofill suggestions for `input` elements with or without an [appropriate field name for the form control][]. As such, the assistive technologies should be able recognize the purpose of a control even when the `autocomplete` [attribute value][] is inappropriate for the control's `type` [attribute value][]. ## Accessibility Support @@ -74,7 +71,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 +79,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 +95,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 +103,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 +111,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 +127,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 +153,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 +195,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 +209,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 +217,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 +225,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 +233,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 +241,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' diff --git a/_rules/block-collapsible-3e12e1.md b/_rules/block-collapsible-3e12e1.md index 96215b4fef2..13bc11c7c6f 100755 --- a/_rules/block-collapsible-3e12e1.md +++ b/_rules/block-collapsible-3e12e1.md @@ -61,7 +61,7 @@ In this document, the [visibility][visible] and [inclusion in the accessibility ```html
- + The Three Kingdoms, Chapter 1 @@ -91,7 +91,7 @@ In this document, the [visibility][visible] and [inclusion in the accessibility ```html - + The Three Kingdoms, Chapter 1 @@ -125,7 +125,7 @@ In this document, the [visibility][visible] and [inclusion in the accessibility ```html - + The Three Kingdoms, Chapter 1 @@ -160,8 +160,8 @@ In this document, the [visibility][visible] and [inclusion in the accessibility ```html - - + + The Three Kingdoms, Chapter 1 @@ -220,8 +220,8 @@ This document has an [instrument][] to toggle [visibility][visible] of the navig ```html - - + + The Three Kingdoms, Chapter 1 @@ -251,7 +251,7 @@ This document has an instrument to toggle [inclusion on the accessibility tree][ ```html - + The Three Kingdoms, Chapter 1 diff --git a/_rules/bypass-blocks-cf77f2.md b/_rules/bypass-blocks-cf77f2.md index 2a41924ad4d..d979bf32557 100755 --- a/_rules/bypass-blocks-cf77f2.md +++ b/_rules/bypass-blocks-cf77f2.md @@ -103,7 +103,7 @@ This [HTML web page][] is passing rule [_Block of repeated content is collapsibl ```html - + The Three Kingdoms, Chapter 1 @@ -407,7 +407,7 @@ This [HTML web page][] is passing rule [_Block of repeated content is collapsibl ```html - + The Three Kingdoms, Chapter 1 diff --git a/_rules/document-has-headings-for-non-repeated-content-047fe0.md b/_rules/document-has-headings-for-non-repeated-content-047fe0.md index e6c3baa2a19..89628883e3f 100755 --- a/_rules/document-has-headings-for-non-repeated-content-047fe0.md +++ b/_rules/document-has-headings-for-non-repeated-content-047fe0.md @@ -201,7 +201,7 @@ This [document][] has a `h1` heading, which is [visible][] and [included in the
- +

Three Heroes Swear Brotherhood at a Feast in the Peach Garden

Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span @@ -262,7 +262,7 @@ This [document][] has a `h1` heading, which is [visible][] and [included in the

Three Heroes Swear Brotherhood at a Feast in the Peach Garden

@@ -360,7 +360,7 @@ The non-repeated content of this [document][] starts with a `h1` heading, but it ```html - + The Three Kingdoms, Chapter 1 diff --git a/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md b/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md index 3f8a8147c79..d17b7e07fc3 100755 --- a/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md +++ b/_rules/document-has-instrument-to-non-repeated-content-ye5d6e.md @@ -167,7 +167,7 @@ In this [document][], the first `a` element is an [instrument][] to move the foc ```html - + The Three Kingdoms, Chapter 1 @@ -197,7 +197,7 @@ In this [document][], the first `div` element is an [instrument][] to move the f ```html - + The Three Kingdoms, Chapter 1 diff --git a/_rules/menuitem-non-empty-name-m6b1q3.md b/_rules/menuitem-non-empty-name-m6b1q3.md index d6fadbcce75..97467ef759d 100755 --- a/_rules/menuitem-non-empty-name-m6b1q3.md +++ b/_rules/menuitem-non-empty-name-m6b1q3.md @@ -35,9 +35,9 @@ This rule assumes that all menuitems are [user interface components as defined b ## Accessibility Support -In some assistive technologies, the `menuitem` role will only be announced in browsing mode. When they receive focus this role is not announced. Additionally, the `title` attribute is not in all circumstance a reliable way to provide an accessible name. Use `aria-label` instead. +In some assistive technologies, the `menuitem` role will only be announced in browsing mode. When they receive focus this role is not announced. Additionally, the `title` attribute is not a reliable way to provide an accessible name. Use `aria-label` instead. -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 `button` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. +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 `menuitem` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. ## Background diff --git a/_rules/video-alternative-for-visual-c5a4ea.md b/_rules/video-alternative-for-visual-c5a4ea.md index 6d711327369..7d1c2a1b932 100755 --- a/_rules/video-alternative-for-visual-c5a4ea.md +++ b/_rules/video-alternative-for-visual-c5a4ea.md @@ -155,7 +155,7 @@ A video element that describes some of the text on the same page. The text on th #### Failed Example 1 -A video element with an incorrect audio description. +This `video` element has an incorrect audio description. ```html From d9e82c940abf6482fffb2abbd26364cebeb5967f Mon Sep 17 00:00:00 2001 From: ajanec01 Date: Sat, 24 Apr 2021 10:50:23 +0100 Subject: [PATCH 15/15] updating with origin --- package-lock.json | 6 +++--- pages/glossary/text-inheriting-language.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/package-lock.json b/package-lock.json index 45d0555c41d..8742f046d5a 100644 --- a/package-lock.json +++ b/package-lock.json @@ -8293,9 +8293,9 @@ "dev": true }, "y18n": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/y18n/-/y18n-4.0.0.tgz", - "integrity": "sha512-r9S/ZyXu/Xu9q1tYlpsLIsa3EeLXXk0VwlxqTcFRfg9EhMW+17kbt9G0NrgCmhGb5vT2hyhJZLfDGx+7+5Uj/w==", + "version": "4.0.3", + "resolved": "https://registry.npmjs.org/y18n/-/y18n-4.0.3.tgz", + "integrity": "sha512-JKhqTOwSrqNA1NY5lSztJ1GrBiUodLMmIZuLiDaMRJ+itFd+ABVE8XBjOvIWL+rSqNDC74LCSFmlb/U4UZ4hJQ==", "dev": true }, "yargs": { diff --git a/pages/glossary/text-inheriting-language.md b/pages/glossary/text-inheriting-language.md index 3d5f381816e..90d296d05c4 100755 --- a/pages/glossary/text-inheriting-language.md +++ b/pages/glossary/text-inheriting-language.md @@ -11,14 +11,14 @@ input_aspects: The _text inheriting its programmatic language_ from an element E is composed of all the following texts: -- **text nodes**: the value of any [text nodes][] that are [visible][] or [included in the accessibility tree][] and children of an element with the same programmatic language as E; -- **accessible text**: the [accessible name][] and [accessible description][] of any element with the same programmatic language as E, and [included in the accessibility tree][]; +- **text nodes**: the value of any [text nodes][] that are [visible][] or [included in the accessibility tree][] and children of an element inheriting its programmatic language from E; +- **accessible text**: the [accessible name][] and [accessible description][] of any element inheriting its programmatic language from E, and [included in the accessibility tree][]; - **page title**: the value of the [document title][], only if E is a [document][] in a [top-level browsing context][]. An element F is an _element inheriting its programmatic language_ from an element E if one of the following conditions is true (recursively): - F is E itself (an element always inherits its programmatic language from itself); or -- F does not have a non-empty `lang` attribute, and is the child in the [flat tree][] of an element with the same programmatic language as E; or +- F does not have a non-empty `lang` attribute, and is the child in the [flat tree][] of an element inheriting its programmatic language from E; or - F is a [fully active][] [document][] element, has no non-empty `lang` attribute, and its [browsing context container][] is an element inheriting its programmatic language from E. [accessible description]: https://www.w3.org/TR/accname-1.1/#dfn-accessible-description 'Definition of Accessible description'