w3c / w3c/csswg-drafts

[mediaqueries-5] image backgrounds vs transparency

Open
#5,671 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

a11y-tracker mediaqueries-5
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

Given the name of prefers-reduced-transparency, I would expect it to be "transparency is bad, but complex backgrounds are totally fine". However, I wanted to check if that's actually a correct interpretation of the accessibility requirement.

(@cookiecrook mentioned that prefers-reduced-transparency derives from a MacOS setting in a context where transparency is often used but background images aren't a thing; but on the Web, they definitely are. So we have this additional thing to consider.)

So the question is, is the requirement that generated prefers-reduced-transparency really about wanting reduced transparency e.g. because of some confusion over whether the obscured content is still relevant, or is it also about reducing decorative visual complexity--including both the use of transparency but also complex background images, such that authors should not be using complex opaque backgrounds either?

If the former (really only about transparency), do we also need an MQ for reducing e.g. patterned or image backgrounds to more subtle or solid effects? (And if so should that really be a separate MQ, given that adding one adds authoring complexity and fingerprinting surface?)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reviewing the current prefers-reduced-transparency requirement and the issue discussion about image backgrounds, opaque backgrounds, and fingerprinting; done means the CSS Working Group records whether the existing media feature covers this case or whether a separate feature is needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
accessibility, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.