[Meta] Track CSS forced-color standardization and browser support

Created on 24 August 2020, over 4 years ago

Updated 15 January 2025, about 1 month ago

Problem/Motivation

The Claro and Olivero themes have several instances of using -ms-high-contrast to apply high contrast specific styles. This does not work in Firefox, and is deprecated in MS Edge.

Meanwhile, implementation of the new forced-colors CSS standard is proceeding well, and it's possible to achieve a similar level of support in Chromium and Firefox browsers.

Proposed resolution

Not necessary or reliable. See comments #7, #11, #15.
Identify some concrete examples of issues where it would be difficult/impossible to support high contrast without the a high contrast identifying script. As of comment #16, none are known.
Determine if the issues are best addressed by refactoring core or using the script. If it's the latter, implement the script.

Remaining tasks

OUTDATED: Olivero is already doing so, and supporting forced colours modes is something all core themes can and should do.

📌 Task

Status

Active

Version

11.0 🔥

Component

CSS

Created by

🇺🇸United States bnjmnm Ann Arbor, MI

Live updates comments and jobs are added and updated live.

Accessibility
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

high contrast

wcag131

forced colors

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 month ago →
🇳🇱Netherlands groendijk
Some discussion about -ms-high-contrast over here too: https://www.drupal.org/project/drupal/issues/3327405 📌 Potentially remove -ms-high-contrast Needs work

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024