Skip to content

Commit 0c8564e

Browse files
WilcoFiersJym77
andauthored
Add 1.1.1 secondary requirement to marked-as-decorative rule (#2224)
* Add 1.1.1 secondary requirement to marked-as-decorative rule * Update _rules/element-marked-decorative-is-not-exposed-46ca7f.md --------- Co-authored-by: Jean-Yves Moyen <jym@siteimprove.com>
1 parent f7117b5 commit 0c8564e

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

_rules/element-marked-decorative-is-not-exposed-46ca7f.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ rule_type: atomic
66
description: |
77
This rule checks that elements marked as decorative either are not included in the accessibility tree, or have a presentational role.
88
accessibility_requirements:
9+
wcag20:1.1.1: # Non-text content (A)
10+
secondary: This success criterion is **less strict** than this rule. Only when this rule is applied to decorative content does a failure of 1.1.1 occur.
911
input_aspects:
1012
- Accessibility tree
1113
- CSS styling
@@ -35,7 +37,7 @@ Elements are normally [marked as decorative][] to convey the intention of the au
3537

3638
Whenever such a conflict occurs, this indicates at the very least mismatching intentions. Such a conflict should be avoided.
3739

38-
When these conflicts arise on [decorative][] [non-text content][], this is also a failure of [Success Criterion 1.1.1: Non-text Content][sc111] because [decorative][] [non-text content][] must be implemented in a way that allows assistive technologies to ignore it. When these conflicts arise on text content, or on content which is not [decorative][], this is not a failure of WCAG. Therefore this rule is not mapping to any specific WCAG Success Criterion, and is not an accessibility requirement for WCAG.
40+
When these conflicts arise on [decorative][] [non-text content][], this is also a failure of [Success Criterion 1.1.1: Non-text Content][sc111] because [decorative][] [non-text content][] must be implemented in a way that allows assistive technologies to ignore it. When these conflicts arise on text content, or on content which is not [decorative][], this is not a failure of WCAG. Therefore this rule maps to Non-text Content as a secondary requirement.
3941

4042
### Assumptions
4143

0 commit comments

Comments
 (0)