- From: Travis Spomer via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jan 2022 00:57:42 +0000
- To: public-design-tokens-log@w3.org
TravisSpomer has just created a new issue for https://github.com/design-tokens/community-group: == High contrast colors == The current draft of the spec allows colors to be specified as `#112233` or `#112233aa`. That would mean that it's impossible to specify a color using the [system colors](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#system_colors) used in high contrast modes. But, it's essential that a CSS file or XAML resources file (or whatever) produced by processing the token file be able to reference those colors, so a user who needs the background of their apps and web pages to be navy blue for readability can achieve that. I propose that the [15 values defined in the system colors section of CSS Color Module Level 4](https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#system_colors) be added: `"ActiveText"`, `"ButtonBorder"`, and so on. Tools could leave those values as-is when exporting to CSS, map them to the equivalent platform-specific value for other platforms (for example, `"Highlight"` in CSS is `"SystemColorHighlightColor"` in WinUI), or interpret them as aliases to hard-coded values (say, `#00ffff`) in a UI design tool such as Figma where mapping them to a system color might not make sense. Without this, organizations that support high contrast accessibility modes would have to use hard-coded colors for those items along with additional data in the `extensions` node, and then have tools that know what to do with that extension data. Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/91 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 January 2022 00:57:44 UTC