Re: [csswg-drafts] [css-color-6] color-contrast() should distinguish foreground and background (#7359)

> the context of the contrast value and an identifier is probably the best practice.
@Myndex got it, that makes sense. I read too much into the presence of Delta-L*, Michelson, and RMS. @svgeesus that's primarily the reason for my statement on not recommending multiple contrast formulas. I should be more clear on what I'm trying to say! Essentially, as @Myndex mentions in #7357, Delta-E L* is similar to relative luminance and may have similar pitfalls. What I want to be cautious about is what constitutes a *supported formula* for `color-contrast()`. If it's a grab-bag of available options, there could be more harm than good (Hick's law). For many designers & developers who are not familiar or interested in learning the nuance of contrast perception and measurement, it can become a hurdle. If a desired objective for having many different formulas is for testing to find a better contrast formula, I don't believe incorporation into a core CSS feature is the right way to go. 

> No, the primary purpose is to ensure fluent readability by setting an appropriate level of lightness contrast.
Yes; I am not in disagreement with this. But considering **this is a w3c specification**, and **WCAG is the w3c's** standards initiative for making the web more accessible (which includes readability of text), I would expect parity in recommendations and formula. This would only be an issue if additional formulas beyond APCA are being considered for this feature.

> Mandating solely WCAG 2.x suggests that it is an acceptable formula; for dark mode, and for many color combinations, it is not.
I'm not recommending mandating 2.x alone. This is a misunderstanding from poor phrasing above -- I completely agree with supporting WCAG 2.x relative luminance and WCAG 3 APCA formulas. I'm aware of WCAG 2.x formulas flaws.

Thank you for sharing the other thread, I realize my comments are more relative to that issue.

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


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

Received on Tuesday, 9 August 2022 16:02:08 UTC