[a11y-request] Issue: CSS Color 5 2022-05-20 > 2022-08-20 (#29) marked as REVIEW REQUESTED

svgeesus has just labeled an issue for https://github.com/w3c/a11y-request as "REVIEW REQUESTED":

== CSS Color 5 2022-05-20 > 2022-08-20 ==
- name of spec to be reviewed: CSS Color Module Level 5
- URL of spec: https://drafts.csswg.org/css-color-5/ or https://www.w3.org/TR/2022/WD-css-color-5-20220428/

- What and when is your next expected transition? Moving to CR around Q3 2022
- What has changed since any previous review? Has not previously had a11y review
- Please point to the results of your own self-review (see https://w3c.github.io/apa/fast/checklist.html): (nothing in [FAST](https://w3c.github.io/apa/fast/checklist.html) seemed relevant)
- Where and how to file issues arising? On [CSSWG repo](https://github.com/w3c/csswg-drafts/issues/) please
- Pointer to any explainer for the spec? Please see [theIntroduction](https://drafts.csswg.org/css-color-5/#intro)

Other comments:

CSS WG would like to draw your attention in particular to [the `color-contrast()` function](https://drafts.csswg.org/css-color-5/#colorcontrast) which automatically calculates the color (from a list of candidate colors) with the highest WCAG 2.1 luminance contrast. 

CSS WG is aware of the existing work to produce a better contrast metric; applauds this work, and hopes to reference it as an option in the `color-contrast()` function when consensus has formed and the calculation has stabilized. Meanwhile though, and despite the known limitations of the WCAG 2.1 luminance contrast formula, this is the one we are referencing for now.

See https://github.com/w3c/a11y-request/issues/29

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

Received on Friday, 20 May 2022 20:25:51 UTC