From 9bc1a8941031af818b682c683078cea7cbd3bec5 Mon Sep 17 00:00:00 2001 From: Jean-Yves Moyen Date: Thu, 25 Apr 2024 14:06:45 +0200 Subject: [PATCH 1/2] Add inapplicable example with empty lang --- _rules/html-page-lang-valid-bf051a.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/_rules/html-page-lang-valid-bf051a.md b/_rules/html-page-lang-valid-bf051a.md index 03e1244548..a5a8c0f4ef 100755 --- a/_rules/html-page-lang-valid-bf051a.md +++ b/_rules/html-page-lang-valid-bf051a.md @@ -138,6 +138,27 @@ This rule does not apply to `svg` elements. ``` +
+## Boundary Examples + +These examples are not normative and not require for consistent implementations. They illustrate limitations and boundaries of the rule. Passed and Inapplicable examples in this category are likely to fail the rule's accessibility requirement, showing how the rule is only a partial test. Testing tools and methodologies are encouraged to be more clever than the rule, and to report the correct outcome for these examples. Therefore, they are not required for consistent implementation. + +### Inapplicable Examples + +#### Inapplicable Example 1 + +This `html` element has an empty `lang` attribute. It is not applicable for this rule, but nonetheless fails [Success Criterion 3.1.1 Language of Page][sc311]. It also fails rule [HTML page has non-empty title](https://www.w3.org/WAI/standards-guidelines/act/rules/b5c3f8/). + +```html + + + I love ACT rules. + + +``` + +
+ [grandfathered tags]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.8 [iso 639.2]: https://www.loc.gov/standards/iso639-2/php/code_list.php 'ISO 639.2: Codes for the Representation of Names of Languages' [region subtag]: https://www.rfc-editor.org/rfc/rfc5646.html#section-2.2.4 'Definition of region subtag' From 4f6b10edb4e7ac4b336abb91246b13557a160be4 Mon Sep 17 00:00:00 2001 From: Jean-Yves Moyen Date: Thu, 25 Apr 2024 14:24:43 +0200 Subject: [PATCH 2/2] Add some boundary examples --- _rules/aria-required-context-role-ff89c9.md | 17 +++++++++++++ _rules/html-page-lang-valid-bf051a.md | 2 +- .../image-non-empty-accessible-name-23a2a8.md | 17 +++++++++++++ ...visible-label-in-accessible-name-2ee8b8.md | 19 +++++++++++++++ .../zoom-text-no-overflow-clipping-59br37.md | 24 +++++++++++++++++++ 5 files changed, 78 insertions(+), 1 deletion(-) diff --git a/_rules/aria-required-context-role-ff89c9.md b/_rules/aria-required-context-role-ff89c9.md index 67461d2e92..813c729c84 100755 --- a/_rules/aria-required-context-role-ff89c9.md +++ b/_rules/aria-required-context-role-ff89c9.md @@ -239,6 +239,23 @@ There is no element with an [explicit role][] different from its [implicit role] ``` +
+## Boundary Examples + +These examples are not normative and not require for consistent implementations. They illustrate limitations and boundaries of the rule. Passed and Inapplicable examples in this category are likely to fail the rule's accessibility requirement, showing how the rule is only a partial test. Testing tools and methodologies are encouraged to be more clever than the rule, and to report the correct outcome for these examples. Therefore, they are not required for consistent implementation. + +### Inapplicable Examples + +#### Inapplicable Example 1 + +This `li` element has an [explicit role][] identical to its [implicit role][] and therefore is not applicable. This nonetheless doesn't follow ARIA specifications since the resulting `listitem` does not have the required context role of `list`. + +```html +
  • List item 1
    • +``` + +
    + [accessibility tree]: https://www.w3.org/TR/act-rules-aspects/#input-aspects-accessibility 'Definition of accessibility tree' [aria 1.2]: https://www.w3.org/TR/wai-aria-1.2/ 'WAI ARIA 1.2 specifications' [content model]: https://html.spec.whatwg.org/multipage/dom.html#concept-element-content-model 'HTML definition of the Content Model' diff --git a/_rules/html-page-lang-valid-bf051a.md b/_rules/html-page-lang-valid-bf051a.md index a5a8c0f4ef..96eb07596a 100755 --- a/_rules/html-page-lang-valid-bf051a.md +++ b/_rules/html-page-lang-valid-bf051a.md @@ -147,7 +147,7 @@ These examples are not normative and not require for consistent implementations. #### Inapplicable Example 1 -This `html` element has an empty `lang` attribute. It is not applicable for this rule, but nonetheless fails [Success Criterion 3.1.1 Language of Page][sc311]. It also fails rule [HTML page has non-empty title](https://www.w3.org/WAI/standards-guidelines/act/rules/b5c3f8/). +This `html` element has an empty `lang` attribute. It is not applicable for this rule, but nonetheless fails [Success Criterion 3.1.1 Language of Page][sc311]. It also fails rule [HTML page has lang attribute](https://www.w3.org/WAI/standards-guidelines/act/rules/b5c3f8/). ```html diff --git a/_rules/image-non-empty-accessible-name-23a2a8.md b/_rules/image-non-empty-accessible-name-23a2a8.md index e4c27e4562..8a27d962dd 100755 --- a/_rules/image-non-empty-accessible-name-23a2a8.md +++ b/_rules/image-non-empty-accessible-name-23a2a8.md @@ -243,6 +243,23 @@ This `img` element is hidden with `visibility: hidden`. ``` +
    +## Boundary Examples + +These examples are not normative and not require for consistent implementations. They illustrate limitations and boundaries of the rule. Passed and Inapplicable examples in this category are likely to fail the rule's accessibility requirement, showing how the rule is only a partial test. Testing tools and methodologies are encouraged to be more clever than the rule, and to report the correct outcome for these examples. Therefore, they are not required for consistent implementation. + +### Passed Examples + +#### Passed Example 1 + +This `img` element has a non-empty [accessible name][]. The name is not descriptive and therefore the image fails [Success Criterion 1.1.1 Non-text content][sc111], but this rule only check for existence of a name. This `img` also fails rule [Image accessible name is descriptive](https://www.w3.org/WAI/standards-guidelines/act/rules/qt1vmo/). + +```html +Neil Armstrong walking on the Moon +``` + +
    + [accessible name]: #accessible-name 'Definition of accessible name' [explicit role]: #explicit-role 'Definition of explicit role' [focusable]: #focusable 'Definition of focusable' diff --git a/_rules/visible-label-in-accessible-name-2ee8b8.md b/_rules/visible-label-in-accessible-name-2ee8b8.md index 88618546b9..3e5c8161fa 100755 --- a/_rules/visible-label-in-accessible-name-2ee8b8.md +++ b/_rules/visible-label-in-accessible-name-2ee8b8.md @@ -196,6 +196,25 @@ This link has no [visible text content][]. ``` +
    +## Boundary Examples + +These examples are not normative and not require for consistent implementations. They illustrate limitations and boundaries of the rule. Passed and Inapplicable examples in this category are likely to fail the rule's accessibility requirement, showing how the rule is only a partial test. Testing tools and methodologies are encouraged to be more clever than the rule, and to report the correct outcome for these examples. Therefore, they are not required for consistent implementation. + +### Passed Examples + +#### Passed Example 1 + +These buttons have text nodes that qualify as [non-text content][] and therefore pass this rule. The accessible names are not descriptive, thus they fail [Success Criterion 1.1.1 Non-Text Content](https://www.w3.org/WAI/WCAG22/#non-text-content). + +```html + + + +``` + +
    + [accessible name]: #accessible-name 'Definition of accessible name' [match characters]: #matching-characters 'Definition of matching characters' [non-text content]: https://www.w3.org/TR/WCAG22/#dfn-non-text-content 'WCAG Definition of Non-text content' diff --git a/_rules/zoom-text-no-overflow-clipping-59br37.md b/_rules/zoom-text-no-overflow-clipping-59br37.md index c9506e26d4..8b645585cb 100755 --- a/_rules/zoom-text-no-overflow-clipping-59br37.md +++ b/_rules/zoom-text-no-overflow-clipping-59br37.md @@ -270,6 +270,30 @@ This [text node][] with the text "Web Content Accessibility Guidelines 2.1" is f Next: Web Content Accessibility Guidelines 2.1 ``` +
    +## Boundary Examples + +These examples are not normative and not require for consistent implementations. They illustrate limitations and boundaries of the rule. Passed and Inapplicable examples in this category are likely to fail the rule's accessibility requirement, showing how the rule is only a partial test. Testing tools and methodologies are encouraged to be more clever than the rule, and to report the correct outcome for these examples. Therefore, they are not required for consistent implementation. + +### Inapplicable Examples + +#### Inapplicable Example 1 + +None of these [text nodes][text node] has an [ancestor][] with `overflow: hidden` or `clip`. On a viewport of 640 by 512 pixels, the texts overlap and become unreadable, thus this fails [Success Criterion 1.4.4 Resize text](https://www.w3.org/TR/WCAG22/#resize-text). This rule only detects clipping, not overlapping. + +```html +
    + Once upon a midnight dreary, while I pondered, weak and weary, Over many a quaint and curious volume of forgotten + lore. While I nodded, nearly napping, suddenly there came a tapping. +
    +
    + As of some one gently rapping, rapping at my chamber door. “’Tis some visitor,” I muttered, “tapping at my chamber + door— Only this and nothing more.” +
    +``` + +
    + [attribute value]: #attribute-value 'Definition of Attribute Value' [ancestor]: https://dom.spec.whatwg.org/#concept-tree-ancestor 'DOM ancestor, 2020/02/13' [bounding box]: https://www.w3.org/TR/css-ui-3/#valdef-box-sizing-border-box