Remove note in F24 about css background images #4823
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This short "in passing" mention in a note about CSS background images appears to introduce a whole new normative requirement by the backdoor, in a technique note, which effectively fails sites that don't provide both a background colour AND background image in their CSS, because users MAY have changed their browser not to load images. This is not covered anywhere else in WCAG, and in many other places WCAG explicitly does NOT care about how users may have modified/changed their browser settings. Not even 1.1.1 mentions the scenario as a particular reason/concern. This note oversteps its remit.
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This short "in passing" mention in a note about CSS background images appears to introduce a whole new normative requirement by the backdoor, in a technique note, which effectively fails sites that don't provide both a background colour AND background image in their CSS, because users MAY have changed their browser not to load images.
This is not covered anywhere else in WCAG, and in many other places WCAG explicitly does NOT care about how users may have modified/changed their browser settings. Not even 1.1.1 mentions the scenario as a particular reason/concern. This note oversteps its remit.
x-ref #4660 (comment)
preview: https://deploy-preview-4823--wcag2.netlify.app/techniques/failures/f24