diff --git a/_rules/presentational-children-no-focusable-content-307n5z.md b/_rules/presentational-children-no-focusable-content-307n5z.md index 1ef8653d4b..a2b1f6627c 100755 --- a/_rules/presentational-children-no-focusable-content-307n5z.md +++ b/_rules/presentational-children-no-focusable-content-307n5z.md @@ -200,21 +200,7 @@ The applicability of this rule does not include elements with an explicit #### Inapplicable Example 4 -The applicability of this rule does not include hidden elements. It only includes presentational elements (through roles with [presentational children][]). These two terms - "hidden" and "presentational" - are often confused. When an element is "hidden", that means that it is completely omitted from the accessibility tree. When an element is "presentational", that means that its semantic role is omitted from the accessibility tree, but its content remains. - -The [ARIA 1.2 specification]https://www.w3.org/TR/wai-aria-1.2/#presentation) mentions this confusion: -
Many individuals erroneously consider role="presentation" to be synonymous with aria-hidden="true"-
... the presentation role causes a given element to be treated as having no role or to be removed from the accessibility tree, but does not cause the content contained within the element to be removed from the accessibility tree.-
An element is marked as decorative if ... it has an explicit role of none or presentation. - -At any rate: this example shows that this rule does not apply to hidden elements. +This example shows that the applicability of this rule does not include hidden elements. The applicability only includes presentational elements (through roles with [presentational children][]). (The difference between "hidden" and "presentational" is discussed in the [ARIA 1.2 specification](https://www.w3.org/TR/wai-aria-1.2/#presentation)). This example is inapplicable, but if it didn't have aria-hidden="true", then it would fail the rule. ```html