Re: [csswg-drafts] [css-color-adjust-1][mediaqueries-5] Fold `forced-colors` and `prefers-contrast`? (#3856)

The CSS Working Group just discussed ``[css-color-adjust-1][mediaqueries-5] Fold `forced-colors` and `prefers-contrast`?``, and agreed to the following:

* `RESOLVED: add the forced value to prefers-contrast`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-color-adjust-1][mediaqueries-5] Fold `forced-colors` and `prefers-contrast`?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3856<br>
&lt;dael> fantasai: I think we're not going to fold them b/c due to web compat we need to keep forced color MQ.<br>
&lt;dael> fantasai: Could add it to trigger when forced-colors is active so you can know if there is a contrast requirement in place.<br>
&lt;dael> emilio: Who ships prefers-contrast? MS?<br>
&lt;dael> Rossen_: yes<br>
&lt;dael> florian: Not convinced this can work. With prefers you're supposed to pick. With forced it's done for you. Knowing something is changed doesn't tell you want to do<br>
&lt;Rossen_> q?<br>
&lt;dael> fantasai: People will likely want to not use gradients or other content layering. Pull back effects with visual complexity. Those changes which aren't colors are things you'd want with low, high and forced contrast<br>
&lt;dael> Rossen_: Synergy between forced-colors and the other prefer properties makes sense for same reason we made initial change for prefers color scheme. Seems reasonable based on forced-color mode people can allow the effect of forced-colors on large parts of content while providing reasonable experience either for contrast or adjust for appropriate color scheme.<br>
&lt;AmeliaBR> q+<br>
&lt;fantasai> I'm suggesting we make @media (prefers-contrast) { ... } handle high, low, and forced contrast mods<br>
&lt;fantasai> s/mods/modes/<br>
&lt;dael> Rossen_: I would argue for this change for similar reasons fantasai pointed out but also to underline that being able to escape large parts of content and do your own thing is important for this feature.<br>
&lt;dael> Rossen_: I think the current contrast hint is missing here and if people do more with prefers-contrast this is a nice addition<br>
&lt;dael> AmeliaBR: I would argue opposite. Important to keep independent. Forced-color mode can force low-contrast. It' snot common. If we treat forced as prefers-contrast people will assume it means high contrast when it's not true. Keeping them independent options recognizes it's more<br>
&lt;florian> I started skeptical, but I now support the proposal<br>
&lt;dael> fantasai: prefers-contrast also can ack. low contrast. forced-colors says I want a particular contrast. Adding it to prefers-contrast add a preference be it high or low. That's why I think it's appropriate.<br>
&lt;dael> AmeliaBR: How works in authoring boolean perspective? Forced-colors is independent and media prefers-content doesn't match?<br>
&lt;fantasai> https://drafts.csswg.org/mediaqueries-5/#prefers-contrast<br>
&lt;dael> fantasai: We add a kewyrod of forced to prefers-contrast. If you use it without anything it means you have a preference be it high or low and the author should respond<br>
&lt;fantasai> prefers-contrast: no-preference | high | low<br>
&lt;fantasai> proposed to make that<br>
&lt;fantasai> prefers-contrast: no-preference | high | low | forced<br>
&lt;dael> florian: Author you can query to prefers-contrast high o prefers-contrast forced and with forced you can reduce visual complexity<br>
&lt;dael> AmeliaBR: With that I'm okay with prop. Need clear authoring guidance to not assume it's in a specific direction<br>
&lt;dael> astearns: I'm hearing support<br>
&lt;dael> astearns: Obj to add the forced value to prefers-contrast?<br>
&lt;AmeliaBR> s/it's/the preference is/<br>
&lt;fantasai> The fact that 'low' and 'high' both exist as values makes that pretty obvious imho<br>
&lt;dael> RESOLVED: add the forced value to prefers-contrast<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3856#issuecomment-642139541 using your GitHub account

Received on Wednesday, 10 June 2020 17:03:24 UTC