2 ms·
The problem is the contrast ratios. The contrast between 0% black and 100% white on a good screen is so high, it physically causes pain, even migraines. Which i
by kuschku 10y ago
The problem is the contrast ratios. The contrast between 0% black and 100% white on a good screen is so high, it physically causes pain, even migraines. Which is why on HDR screens, the colors of CSS are actually limited to avoid ever going darker than grey or brighter than grey, and the contrast is still very large.
#000000 on a cheap screen is equivalent to #666666 on an HDR screen, #ffffff on a cheap screen is equivalent to #aaaaaa on an HDR screen.
So if a designer uses something that looks exactly like newspaper contrast to them, it’ll look unreadable on a cheap screen.
- twanvl 10y ago> The problem is the contrast ratios. The contrast between 0% black and 100% white on a good screen is so high, it physically causes pain, even migraines. Maybe that means you need to turn down your screen's brightness.
- kuschku 10y agoNo, that’d be exactly the wrong solution. Because then displaying color-calibrated content on your display (such as movies, games, photos) is also completely distorted. Instead, we need a way to specify CSS colors relative to a colorspace and contrast ratio.
- leni536 10y ago>CSS colors It's called sRGB and it supposedly has a "black point" which is not entirely black. Nobody uses it though, on photos it would be useless. Also for me black on white is perfectly fine in a well lit room. White on pitch black is indeed problematic. Anyway, it could be a user/browser preference instead of a designer preference. Lowering brightness shouldn't distort color-calibration too. You are supposed to match your brightness to the surrounding lighting too.
- kuschku 10y ago> Lowering brightness shouldn't distort color-calibration too. You are supposed to match your brightness to the surrounding lighting too. Correct, but it requires recalibration if you lower the brightness (as no screen has a perfectly flat curve)