Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Boundary / Verbose examples #2185

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from
Draft

Boundary / Verbose examples #2185

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9bc1a89
Add inapplicable example with empty lang
Jym77 Apr 25, 2024
4f6b10e
Add some boundary examples
Jym77 Apr 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _rules/aria-required-context-role-ff89c9.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,6 +239,23 @@ There is no element with an [explicit role][] different from its [implicit role]
</ul>
```

<details>
<sumary>## Boundary Examples</sumary>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<sumary>## Boundary Examples</sumary>
<summary>## Boundary Examples</summary>


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.
Copy link
Collaborator

@giacomo-petri giacomo-petri Jun 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
These examples are not normative and not required 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.

typo, applies to all examples


### 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
<li role="listitem">List item 1</li>
```

</details>

[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'
Expand Down
21 changes: 21 additions & 0 deletions _rules/html-page-lang-valid-bf051a.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,27 @@ This rule does not apply to `svg` elements.
<svg xmlns="http://www.w3.org/2000/svg" lang="fr"></svg>
```

<details>
<sumary>## Boundary Examples</sumary>

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 lang attribute](https://www.w3.org/WAI/standards-guidelines/act/rules/b5c3f8/).

```html
<html lang="">
<body>
I love ACT rules.
</body>
</html>
```

</details>

[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'
Expand Down
17 changes: 17 additions & 0 deletions _rules/image-non-empty-accessible-name-23a2a8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,6 +243,23 @@ This `img` element is hidden with `visibility: hidden`.
</div>
```

<details>
<sumary>## Boundary Examples</sumary>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<sumary>## Boundary Examples</sumary>
<summary>## Boundary Examples</summary>


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
<img alt="Neil Armstrong walking on the Moon" src="/test-assets/shared/w3c-logo.png" />
```

</details>

[accessible name]: #accessible-name 'Definition of accessible name'
[explicit role]: #explicit-role 'Definition of explicit role'
[focusable]: #focusable 'Definition of focusable'
Expand Down
19 changes: 19 additions & 0 deletions _rules/visible-label-in-accessible-name-2ee8b8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,25 @@ This link has no [visible text content][].
</a>
```

<details>
<sumary>## Boundary Examples</sumary>

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
<button aria-label="Save">&lt;</button>
<button aria-label="Close">&gt;</button>
<button aria-label="Hello world">X</button>
```

</details>

[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'
Expand Down
24 changes: 24 additions & 0 deletions _rules/zoom-text-no-overflow-clipping-59br37.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,30 @@ This [text node][] with the text "Web Content Accessibility Guidelines 2.1" is f
<a href="/"> Next<span class="mobile-hidden">: Web Content Accessibility Guidelines 2.1</span> </a>
```

<details>
<sumary>## Boundary Examples</sumary>

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
<div style="overflow: visible; height: 1.5em; font-size: 16px;">
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.
</div>
<div>
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.”
</div>
```

</details>

[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
Expand Down
Loading