Re: [csswg-drafts] [css-color] Mitigating fingerprinting for AccentColor/AccentColorText (#10372)

Yup. The way I see it, tainting and not tainting are the two ends of the quantization spectrum, but there can be many intermediate solutions in between.

A particularly dangerous outcome is when the fake color and the real one differ so significantly, that they have different a11y characteristics, which could end up producing inaccessible UIs if authors compute things based on tainted values and use them alongside real ones. That hints towards at least _some_ granularity. 

I also wonder if there is a way to detect whether the accent color is set to a fixed OS default and not taint in that case. I suspect not, but figured I'd throw it out there, in case.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10372#issuecomment-3608216125 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 3 December 2025 18:23:33 UTC