Skip to content

Add 1.1.1 secondary requirement to marked-as-decorative rule #2224

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

Merged
merged 3 commits into from
Feb 7, 2025
Merged

Add 1.1.1 secondary requirement to marked-as-decorative rule #2224

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e286d57
Add 1.1.1 secondary requirement to marked-as-decorative rule
WilcoFiers Nov 7, 2024
fb010af
Update _rules/element-marked-decorative-is-not-exposed-46ca7f.md
WilcoFiers Nov 21, 2024
54fe28d
Merge branch 'develop' into marked-as-decorative-secondary
Jym77 Feb 7, 2025
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
4 changes: 3 additions & 1 deletion _rules/element-marked-decorative-is-not-exposed-46ca7f.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ rule_type: atomic
description: |
This rule checks that elements marked as decorative either are not included in the accessibility tree, or have a presentational role.
accessibility_requirements:
wcag20:1.1.1: # Non-text content (A)
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.
input_aspects:
- Accessibility tree
- CSS styling
Expand Down Expand Up @@ -35,7 +37,7 @@ Elements are normally [marked as decorative][] to convey the intention of the au

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

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.
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.

### Assumptions

Expand Down