- From: Alice via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jul 2020 07:45:12 +0000
- To: public-css-archive@w3.org
Thanks for the explanation on `forced-colors`. > I think it the number of sites that intent to have an enhanced contrast design in the manner of macOS/gmail, and to respond to forced colors, and to have on top of that a very high contrast mode separate from the forced color mode, is likely very small. I think where sites already have multiple themes, it actually wouldn't be a stretch to imagine them having both an "increased" contrast and a "high" contrast theme[1]. That said, I agree that forcing authors to type `@media (prefers-contrast: increase) or (prefers-contrast:high)` is probably best avoided. Honestly, though, I don't know that they should be matching both in any case. I am not sure either way whether users who prefer AAA-level contrast would prefer to see VS Code style high contrast compared to a baseline experience. I think that is a question we should maybe look into[1]. If it turns out they do, then something along the lines of your last proposal here would work well; otherwise, we can just leave out the last sentence. I would prefer to avoid conflating the ideas of enhanced/AAA contrast and high contrast if we can, but as long as we can carefully document that "high" is shorthand for "increased", I can probably live with it. [1] with the obvious caveat that sites have no incentive to provide a true high contrast theme, since there is no automatic way for a user to opt in to it without also having forced colours. -- GitHub Notification of comment by alice Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2943#issuecomment-666197460 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 07:45:14 UTC