Posted by paddingtone 8 hours ago
The WCAG 2 contrast checker is known to be inaccurate, specifically for light on dark color combinations (i.e. dark mode) meaning 4.5:1 isn't always going to be easy to read so it's surprising they're not at least using a higher ratio. The APCA contrast checker (was being considered for WCAG 3) is more accurate at measuring readable contrast levels and the docs explain the problems with WCAG 2 more:
https://git.apcacontrast.com/documentation/APCAeasyIntro.htm...
- Checking "Enable remote debugging" and "Enable chrome and add-on debugging toolboxes" in devtools settings, opening Browser Toolbox (Ctrl+Shift+I), and looking at the "Network" tab
or
- Enable add-on debugging and inspect the addon from `about:debugging`
Worse: it’s attacking you
Worst: it’s attacking someone else as you
Sounds like the Noir dev is going to be the next victim of Apple's Sherlocking.
Today it is!
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/V...
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/A...
I know some people care about dark mode (and that's why I bit the bullet to add it), but I'd honestly much rather have spent all that time working on actual features.
I'm sure there are designers that love dealing with two themes, and will do beautiful work within each theme.
But I'm really fine with letting the computer figure it out. CRM, back office tools, admin dashboards... many clients are approving one design and dark mode is an afterthought. Why can't the computer just... do it for me, and do a better than passable job at that.
The other was Github's icon. But `filter: invert(1)` does a pretty decent job of handling that as long as the icons are black and white.