Possible to disable OS-level High Contrast alterations?

[comp615]

As I read the spec, and the Microsoft implementation, it seems like high-contrast color alterations are applied by the browser as a sort of media query. Then on top of these browser changes, we as developers can apply our own media queries to override those.

My question is about the dreaded css-in-js debate. At Twitter, we do not use media queries and are strict css-in-js via React Native styles. Thus for handling something like night mode, or high contrast night mode, we simply swap our color palette and re-render. I worry that in Windows high-contrast mode, the OS would still apply its enhancements on top of our specific theme.

I know that we can simply run the media query to see if we should use our high contrast palette, but is there a way to then signal that the OS should skip applying any special formatting?

Thanks!

[dpierangeli]

It seems that you can use
<style> * { high-contrast-adjust: none; } </style>

in CSS to opt-out of the High Contrast.

Since * is not performance optimal maybe the high-contrast-adjust property could use a inherit value

• default on all elements 'inherit'
• default on body 'auto'

With this opting-out could be
<style> body { high-contrast-adjust: none; } </style>

[atanassov]

@comp615 This is a valid question and the solution is as described by @dpierangeli.

We allow authors to disable high-contrast (now know as forced-colors) by declaring forced-colors-adjust: none on any element and its effect applies to the element and its entire subtree. In other words, when applied to the root effectively no forced-colors will be applied.

[atanassov]

Considering the topic closed at this point.