- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Apr 2019 23:29:03 +0000
- To: public-css-archive@w3.org
I don't think we should be confusing `forced-colors` and `prefers-contrast` at all. If there is authoring advice that is specific to creating good contrast, it should go under the `prefers-contrast` MQ. A `forced-color` setting (as currently defined) is going to turn off text shadows and block out busy backgrounds behind text, anyway, so I'm not sure why this extra advice is necessary.
Now, it may make sense to combine `prefers-reduced-transparency` and `prefers-contrast`. But then, I'm not quite sure who's asking for the reduced transparency case — the MacOS no-transparency setting is as much a performance option as it is an accessibility one.
I _do_ think web browsers should automatically update the `prefers-contrast` state automatically if they can correctly deduce that the forced color scheme is high/low contrast.
("correctly" being the key point. WHCM can't even figure out if my custom color scheme is dark-on-light or light-on-dark & doesn't give me any way to specify it — it's a hidden setting based on whichever built-in color scheme you started with before you customized it. grumble grumble grouch…)
> Basically, I think it'd be nice if authors could have very clear triggers for when to make what adjustments,
This, I very much agree with.
--
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3856#issuecomment-485196310 using your GitHub account
Received on Saturday, 20 April 2019 23:29:05 UTC