- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Feb 2021 23:47:06 +0000
- To: public-css-archive@w3.org
> we may come to the same disagreement about whether there is a correlation between "non more/less contrast but forced colors" and a desire for reduced visual complexity. @fantasai made the argument very well during the meeting that these two concepts correlate *by definition*: whether you prefer high-contrast, low-contrast, or have a forced color scheme, you are reducing the available space of colors for the page to use. Low-contrast wants the page to more closely-clustered colors, avoiding extremes from using colors far apart in color space; high-contrast wants the opposite, using more extreme colors and avoiding closely-clumped ones; forced-colors gives you about a dozen colors *total* that you are allowed to use. In all these cases, because your available set of colors is reduced, you usually want to reduce visual complexity. * In high-contrast, subtle gradients and shadows are the precise opposite of what the user is asking for; the page should use simpler color blocks and borders to indicate visual hierarchy more obviously instead. * Low-contrast is typically *also* associated with a desire for simpler pages, from what I understand of the a11y needs underlying it; it's typically a sensory-processing issue, and again, simpler, plainer visual hierarchy can usually serve their needs better. Even ignoring that, just the fact that you have a narrower band of colors to work with means you can't rely on having as many distinguishable color/lightness levels, and must instead design your page to indicate hierarchy and importance in ways that don't rely as much on color. * And finally, in forced-colors you simply don't have many colors to play with, and you don't know what they are anyway, so you can't usefully counterpoint them; again, a simpler visual hierarchy is the obvious way to work around the limitations you're saddled with. Several of us have repeatedly made this argument, and even provided rendering examples showing off the issues we're talking about. It's felt as if your responses have mostly been "I disagree", which has proven frustrating; there's nothing we can discuss there. > because the force color scenarios that would need reduced complexity would already match either more or less contrast... I don't understand what forced-colors scenario could possibly *not* want reduced visual complexity. Forced colors needs reduced visual complexity *because the colors are forced and from a small palette* - the actual identity of the colors doesn't factor into this at all, as far as we can tell. Can you give an example of a forced-colors palette that you think would *not* benefit from reduced visual complexity (or rather, that wouldn't be harmed by leaving a reasonably-high visual complexity page alone while applying the forced colors), but would if we tweaked the colors to be higher or lower contrast? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6036#issuecomment-786308318 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 February 2021 23:47:07 UTC