Intent to Ship: Media Queries: prefers-reduced-transparency feature

Skip to first unread message


Jul 21, 2023, 5:21:40 PM7/21/23

Contact emails





Adds the `prefers-reduced-transparency` feature, which lets authors adapt web content to user-selected preference for reduced transparency in the OS, such as the 'Reduce transparency' setting on macOS. Valid options are 'reduce' or 'no-preference'.

Blink component


Search tags


TAG review


TAG review status

Not applicable


Interoperability and Compatibility

Gecko: No signal ( There is a separate umbrella issue for some the preference media queries (contrast, motion, color-scheme). They have a stale PR to add an overall positive position for those preference media queries. They also have an implementation behind a flag. It's not been enabled yet due to fingerprinting concerns.

WebKit: No signal ( I have submitted an implementation of this feature as a PR to WebKit:

Web developers: Positive (

Other signals:


This feature can be used for fingerprinting as it exposes a user preference.

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?


This can be emulated in the Dev Tools rendering tab like other preference media queries.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?


The feature will be supported on all platforms, but whether the user will be able to signal a reduced transparency preference may depend on the OS.

Is this feature fully tested by web-platform-tests?


Flag name on chrome://flags


Finch feature name


Requires code in //chrome?


Tracking bug

Sample links

Estimated milestones

Shipping on desktop117
DevTrial on desktop117
Shipping on Android117
DevTrial on Android117

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

Link to entry on the Chrome Platform Status

Links to previous Intent discussions

Intent to prototype:

This intent message was generated by Chrome Platform Status.

Yoav Weiss

Jul 24, 2023, 4:14:13 AM7/24/23
to Luke, Mike Taylor, blink-dev
I'd love to hear +Mike Taylor 's thought about this from an extra fingerprinting bit perspective. Also, how would users signal their preference?

You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To view this discussion on the web visit


Jul 24, 2023, 4:29:06 AM7/24/23
to blink-dev,, blink-dev, Luke,
> Also, how would users signal their preference?

There are currently three platforms that implement an explicit setting for this preference.
  • In Windows 10/11: Settings > Accessibility > Visual effects > Transparency effects.
  • In macOS: System Preferences > Accessibility > Display > Reduce transparency.
  • In iOS: Settings > Accessibility > Display & Text Size > Reduce Transparency.
I don't have access to Chrome OS and as such can't be sure on if there's a setting for this but based on the fact Android doesn't have one and I couldn't find documentation I've assumed there isn't.

Currently the implementation is written to follow the Windows and macOS setting, and iOS can be added trivially in future once the blink development is further along on iOS. On platforms with no explicit setting users currently cannot indicate their preference. However, I would like to see browser level control of this (and other preference media queries) in future.

Mike Taylor

Jul 26, 2023, 11:28:42 AM7/26/23
to Yoav Weiss, Luke, blink-dev, Tab Atkins-Bittner

As to the fingerprintability, we should think about the trade-offs we're making between accessibility and adding more active surfaces that give away some bits of entropy. I'd love to hear more about requests from the a11y or developer community to actually have this MQ available to them. My own take is that if it can benefit some users, and sites will use it, the incremental entropy available here is probably acceptable.

I note that is effectively empty, with an inline issue saying ~"TODO: figure out if these are OK". That doesn't seem super great. Do we know if there is consensus among editors on the utility vs privacy trade offs of these MQs? (Maybe Tab can chime in on this topic...).

Based on, it doesn't seem like there's a lot of appetite from Apple or Mozilla.


Jul 26, 2023, 12:27:27 PM7/26/23
to blink-dev,, blink-dev, Tab Atkins-Bittner,, Luke
> ...effectively empty, with an inline issue saying ~"TODO: figure out if these are OK".

I've added a comment to an existing CSS spec issue regarding that issue section. 

> Based on, it doesn't seem like there's a lot of appetite from Apple or Mozilla.

There's mixed signals from Mozilla and especially Apple imo.

While Apple have added a general concerns label for all `prefers-*` media queries, they've also implemented at least 3 of them along with being the only UA to currently expose `inverted-colors` information. They've also made 1 of the two current issues regarding potential new preference media queries (namely prefers-reduced-strobing)

Mozilla likewise don't seem overly keen on prefers-reduced-transparency (a third party implemented it recently but so far it remains disabled by default) but have also exposed the 3 existing prefers media queries along with also implementing `forced-colors` (Apple has too but it always evaluates to false so isn't relavant). They also started a PR to add a supportive position for the preference media queries given their accessibility benefits.

> My own take is that if it can benefit some users, and sites will use it, the incremental entropy available here is probably acceptable.

I would agree if there's an improved accessibility experience it's worth the privacy tradeoff imo. As for how useful users and site authors would find it I'm not sure how best to go about finding that out. There's various blog posts mentioning it, and obviously there must be some benefit to exposing the settings else Microsoft and Apple wouldn't have explicit settings for it. Potentially some a11y specialists could chime in on this front?


Jul 31, 2023, 1:41:45 PM7/31/23
to blink-dev, Luke,, blink-dev, Tab Atkins-Bittner,
Is there anything more I can do to help move this conversation forward? I would try to gather a consensus that authors would use it but I don't have a following large enough to gather anything valuable.

David Bolter

Aug 1, 2023, 10:56:25 AM8/1/23
to blink-dev, Luke,, blink-dev, Tab Atkins-Bittner,
I agree with Mike that the incremental entropy available is probably acceptable. I don't have any data/awareness of demand for this setting but it is at least some signal that it is available on Windows, Mac, iOS (thanks Luke). I'll ping some folks and come back (or they will) if there is info to share.

Chris Harrelson

Aug 1, 2023, 7:03:46 PM8/1/23
to David Bolter, blink-dev, Luke,, Tab Atkins-Bittner,
Hi Luke, could you file for a TAG review for this feature?


Aug 1, 2023, 8:13:08 PM8/1/23
to blink-dev, Chris Harrelson, blink-dev, Luke,, Tab Atkins-Bittner,, David Bolter I've filed a tag review (hopefully filled it all out correctly)

Mike Taylor

Aug 9, 2023, 11:56:48 AM8/9/23
to Luke, blink-dev, Chris Harrelson, Tab Atkins-Bittner,, David Bolter


Daniel Bratell

Aug 9, 2023, 1:53:35 PM8/9/23
to Mike Taylor, Luke, blink-dev, Chris Harrelson, Tab Atkins-Bittner,, David Bolter

Chris Harrelson

Aug 16, 2023, 1:24:50 PM8/16/23
to Daniel Bratell, Mike Taylor, Luke, blink-dev, Tab Atkins-Bittner,, David Bolter
Reply all
Reply to author
0 new messages