- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Feb 2020 03:44:46 +0000
- To: public-css-archive@w3.org
> they may just want to change a singular property value without interfering with other UA forced color styles This seems like a dangerous thing to do, anyway. If an author changes foreground but not background colors (or vice versa) based on what they _expect_ a "high contrast" mode to do, it could break very badly in a different forced colors mode. The specific case of being able to indicate grayed text, using system colors, is valid, but is it really that much harder to also set the `forced-colors-adjust: none` and the matching background color (buttonFace or field)? There's also nothing stopping a UA stylesheet from selecting on ARIA attributes when applying the forced color mode, if you're seeing this problem (ARIA semantics being lost in high contrast) a lot in the wild. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4178#issuecomment-582227152 using your GitHub account
Received on Wednesday, 5 February 2020 03:44:48 UTC