[w3ctag/design-reviews] WG Revision: CSS Color Adjust Level 1 (Issue #1156)

alisonmaher created an issue (w3ctag/design-reviews#1156)

### Specification

https://www.w3.org/TR/css-color-adjust-1/

### Explainer

https://

### Links

- The WG's request for this TAG review: https://github.com/w3c/csswg-drafts/issues/12815#issuecomment-3303636441
- TAG review of the previous version of this specification, if any: https://github.com/w3ctag/design-reviews/issues/583
- A description of what has changed since our previous review: https://www.w3.org/TR/css-color-adjust-1/#changes
NOTE: that there is one additional change since CRD was republished that I will try to incorporate with the final CRS republication. The change description link is still relevant for this PR, this is just an editorial clarification based on implementor feedback: https://github.com/w3c/csswg-drafts/pull/12892/files


Feature 1:
- Previous early design review, if any: N/A
- An introduction to the feature, aimed at unfamiliar audiences: https://github.com/w3c/csswg-drafts/issues/11824
- A description of the problems that end-users were facing before this proposal: This feature does not impact end users, but allows implementors to test forced colors mode within the WPT test suite. The main way to trigger forced colors mode is through the Windows contrast theme system setting. In order to emulate this feature for testing purposes, webdriver support was added to the spec.
- Alternatives considered: N/A
- Examples of how to use the proposal to solve the end-users' problems: N/A
- What do the end-users experience with this proposal: N/A
- User research you did to validate the problem and/or design, if any: N/A
- Web Platform Tests:  N/A (there are wpt tests for forced colors mode, but they have yet to be updated to use the new web driver API)

Feature 2:
- Previous early design review, if any: N/A
- An introduction to the feature, aimed at unfamiliar audiences: https://github.com/w3c/csswg-drafts/issues/8064
- A description of the problems that end-users were facing before this proposal: Foreground and background colors for text on the page was updated to guarantee the user's preferred color contrast in forced colors mode, but emojis did not honor these colors, creating less overall contrast. The proposal was to force emojis to their monochrome variant in forced colors mode if available to guarantee the same level of contrast with other text on the page.
- Alternatives considered: Leaving emojis as they are rendered without forced colors mode.
- Examples of how to use the proposal to solve the end-users' problems: This happens automatically, but can be opted out by an author using `forced-color-adjust: none`
- What do the end-users experience with this proposal: The second set of emojis depicted in https://github.com/w3c/csswg-drafts/issues/8064#issue-1445817393
- User research you did to validate the problem and/or design, if any: This was proposed based on user feedback to forced colors mode, and matches how EdgeHTML used to render emojis in high contrast mode.
- Web Platform Tests: This is being implemented in Chromium, but hasn't landed yet. WPTs will be added along with this work.

NOTE: all other edits were minor and well described in the changes link.


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [x] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/w3c/csswg-drafts
- Primary contacts:
  - Alison Maher (@alisonmaher), Microsoft
  - Elika Etemad (@fantasai), Apple
  - Tab Atkins Jr (@tabatkins), Google
- Organization/project driving the specification: See above
- This work is being funded by: See above
- Primary standards group developing this feature: CSSWG
- Incubation and standards groups that have discussed the design: N/A

### Feedback so far

- Active horizontal reviews: https://github.com/w3c/csswg-drafts/issues/12815
- Multi-stakeholder feedback: N/A
- Major unresolved issues with or opposition to this specification: N/A, but as noted above, there was one recent PR that landed that is an editorial clarification based on implementor feedback that I will try to incorporate into the republished CRS, as well (https://github.com/w3c/csswg-drafts/pull/12892/files)
- Status/issue trackers for implementations: Most of the updates are related to forced colors mode, which are not relevant to Webkit.

For the Forced Colors Mode Webdriver Change:
- CRBug: https://issues.chromium.org/issues/434861608
- Bugzilla links: https://bugzilla.mozilla.org/show_bug.cgi?id=1980877, https://bugzilla.mozilla.org/show_bug.cgi?id=1980876

For the Forced Colors Mode Emoji Change:
- CRBug: https://issues.chromium.org/issues/420857717
- Bugzilla link: https://bugzilla.mozilla.org/show_bug.cgi?id=1992799

All other changes did not require implementor updates.

### You should also know that...

We are looking to republish CRS for CSS Color Adjust 1 with the updates mentioned above in the next month or so

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1156


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1156
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1156@github.com>