Re: [csswg-drafts] [css-forms-1] Account for forced-colors mode (#12060)

> I'm not familiar with the reasoning for the different options in windows contrast themes but the fact button background and test colours are configurable makes me think we should honour them. Even in base mode.

Using system colors should be sufficient to get high contrast themes honored. I think we should do this only behind a forced-colors media query though.

> I think in practice border-color can be set to ButtonText and that would be fine. Windows only actually lets you customise a foreground and background colour for "buttons" (I think it actually should apply to at least select and other button like elements too). Though maybe ButtonBorder is better to allow for other forms of forced colors with more granularity.

ButtonBorder probably makes sense here. It'll probably set to ButtonText on Windows anyway.

> We might also need this so the colour Swatch renders correctly? (Not sure exactly how forced colors applies to UA styles).
> 
> ::color-swatch {
>    forced-colors-adjust: none;
> }


> There's also some thought needed for the disabled states (and I guess placeholder too) such that they might need to use GrayText system colour to be styled correctly.

GrayText for disabled states is what's typically used. Placeholder should just use currentColor/inherit in forced colors mode, I _think_ that's what Windows does.

> It would also be good to consider stuff like hover and active states and see if they'd need any special handling.

Last I remembered, hover uses the `Highlight`/`HighlightText` pair.

-- 
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12060#issuecomment-2789492487 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 April 2025 12:11:38 UTC