W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2020

Re: [csswg-drafts] [mediaqueries-5] prefers-contrast: infer contrast preference from forced colors (#5224)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 30 Jul 2020 17:00:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-666526051-1596128437-sysbot+gh@w3.org>
The CSS Working Group just discussed `Inferring contrast preference from forced colors`, and agreed to the following:

* `RESOLVED: no change: not defining contrast thresholds`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Inferring contrast preference from forced colors<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/5224<br>
&lt;fantasai> florian: When you have forced colors<br>
&lt;fantasai> florian: when the user has said "I want this foreground color and that background color"<br>
&lt;fantasai> florian: There is guidance that if the UA knows if that combination is high contrast, should match (prefers-contrast: high)<br>
&lt;fantasai> florian: and if combo is low contrast, should match (prefers-contrast: low)<br>
&lt;fantasai> florian: Question is what's the thresholds<br>
&lt;fantasai> florian: We have a known set of colors here from the user, so we can calculate the ratio<br>
&lt;fantasai> florian: maybe we want interop among browsers?<br>
&lt;fantasai> florian: one possibility is to hook into WCAG levels<br>
&lt;fantasai> florian: but WCAG is AAA is about high contrast enough to be readable, not very high contrast<br>
&lt;fantasai> florian: and WCAG AA is reasonably high contrast<br>
&lt;Rossen_> q+<br>
&lt;fantasai> florian: If we want a number, I suspect these aren't the ones we want<br>
&lt;astearns> ack fantasai<br>
&lt;astearns> ack Rossen_<br>
&lt;fantasai> fantasai: I propose leaving this up to the UA, to allow experimentation and let browsers figure out the good answers<br>
&lt;fantasai> fantasai: Maybe revisit a few years in the future.<br>
&lt;fantasai> Rossen_: I say, yes, definitely the browser should do this<br>
&lt;fantasai> Rossen_: wrt what are the ratios<br>
&lt;fantasai> Rossen_: there are some guidelines, e.g. Microsoft has some guidelines for contrast ratios in all of our products<br>
&lt;fantasai> Rossen_: Fairly in line with WCAG<br>
&lt;florian> q?<br>
&lt;fantasai> Rossen_: However we decide on the precise values, I don't believe we're the group for deciding that<br>
&lt;fantasai> Rossen_: Not sure it's the browsers themselves, but some combination of a11y WG or WCAG as well as some of the companies who own a11y guidelines<br>
&lt;fantasai> Rossen_: Together should be able to figure it out<br>
&lt;fantasai> Rossen_: I also agree, let's not have specific numbers<br>
&lt;fantasai> fantasai: Propose closing no change, we will not define here. Maybe in 3-5 years we can revisit.<br>
&lt;fantasai> Rossen_: Maybe referencing ohter things like WCAG<br>
&lt;fantasai> florian: I don't think WCAG is appropriate reference, it's guideline for general contrast, not high contrast<br>
&lt;fantasai> RESOLVED: no change: not defining contrast thresholds<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 July 2020 17:00:40 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:12 UTC