Re: [csswg-drafts] [mediaqueries-5] Remove (prefers-contrast) as a boolean, and replaced by a new color reduction media query (#6036)

For me, this issue comes down to whether or not the range between `more` and `less` is considered a valid contrast preference. Depending on the answer to this, we can narrow down potential options for a path forward.

### If we agree that the range in between `more` and `less` is **NOT** a valid contrast preference, then we should not add back `forced`. This leaves us with the following options:
1. Leave everything as-is (i.e. don’t add any new media queries or new keywords to `prefers-contrast`).
2. Look into adding a new media query to encapsulate the various intersections of existing media queries (forced-colors, prefers-contrast, etc.) similar to what is being suggested here by @FremyCompany .

### If we agree, however, that the range in between `more` and `less` represents a valid contrast preference, we have the following options:
1. Add a third value (name TBD) that strictly represents the contrast range between `more` and `less`.
2. Adjust the cut-off between `more` and `less`, similar to what @dlibby- mentioned in https://github.com/w3c/csswg-drafts/issues/6036#issuecomment-799861439, to ensure that the two values cover all possible ranges of contrast ratios.
3. Add back `forced` to capture users who lie in the middle range in forced colors mode.

If we were to add `prefers-contrast: forced`, I think that we would also need to add `prefers-color-scheme: forced` for consistency, since both are affected by forced colors mode. This would add even more confusion for authors. For this reason and for the various reasons outlined in #5433, my preference in this case would be for option 1 or 2.

And as a note, we'd like to ship `prefers-contrast` to better serve users with a contrast preference on non-Windows platforms, but we'd like to get clarity on this issue before proceeding given that there is still a divide on the best path forward.

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


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

Received on Wednesday, 14 April 2021 00:18:23 UTC