The "safe" rule would be to use 100% black and 100% white for maximum contrast. Only diverge from that if you have a good reason.
TBF, I think having a small range of blacks in use is a good thing. Use 0.0 and 1.0 for highlighted items. 0.1 and 0.9 for the rest. Great! A little color rather than grayscale? Great!
But, I've seen far too many sites that take it too far and think they are smart by presenting dim-on-grey text. f2 hex is 0.87 and 22 hex is 0.33. That's cutting my screen's range in half! And, that's much better than many lovingly designed sites I've had stomp over with screen-reader mode, on my 800 nits phone screen!
Or if their device is even capable of it (phones/tablets and laptops)
For a parallel, mplayer lets me adjust these and I use it often because video is just as inconsistent.
Also can't control if a user has their brightness too low. So what then?
People over the age of 30 can mostly read books and newspapers just fine, and when they can't it's rarely the fault of the off-white paper and slightly faded ink.
That said, even though monitors like laptops and phones increase brightness, that’s not enough when in direct sunlight. There, black in white would make sense, but of course comes at a cost of reducing range (it’s physically impossible). Screens that are incapable of keeping up with direct sunlight should probably increase contrast in those conditions.
(Incidentally I'm a big gamer but I generally prefer to turn off HDR because it hurts my eyes. It's actually really annoying. I don't want certain parts of a scene to be extra-extra-bright.)
If you're giving me text, please don't second-guess whether I've set my monitor brightness appropriately. The vast majority of text I look at is already black-on-white. By reducing the contrast of your text you're assuming that everything else I look at is blinding me and somehow you're saving me with more appropriate contrast. No, I've set my monitor so everything else I look at looks right and what you're showing me is too washed out.
Why would #000 text on #fff be the correct way? It’s common but not at all ubiquitous, there’s no standard for this.
> No, I've set my monitor so everything else I look at looks right and what you're showing me is too washed out.
If you don’t like the extra range you can easily increase the contrast and reduce the brightness, but the other way is very destructive. You can go from #def -> #fff with a simple transform but you can’t go the other way. And if you use 100% of your range in a single element, you have no room for using color, shadows and background, which is a critical tool for all complex design, including old school Windows and Mac UIs from the 90s.
That said, there should be better APIs/standardization and monitors should be better at adjusting brightness and contrast to lighting conditions. I don’t mind at all that people change to whatever suits them, in fact I wish it was easier to use things like reader mode (which ad-tech has been fighting against, hard). Lots of web sites suffer from all kinds of design issues these days, sometimes too low contrast, even for me.
Do you have any links to the studies by those researchers? My own understanding is that yellow-on-blue is traditionally meant to be the most visible option, but that there's not actually a huge amount of evidence to back this up, and it's more tradition than anything else right now.
Too much contrast has never been an issue, which is why no one uses flux or dark themes, right?
f.lux is for increasing color temperature. Dark themes are for reducing the ratio of bright to dark. Neither is primarily intended for reducing contrast.
It's relatively easy, by turning #ffffff and #000000 both closer to #ff0000, or in other words, by reducing the contrast.
Dark themes (excluding amoled themes) exist to reduce the perceived contrast between the screen and the environment.
In both cases, either directly or indirectly, contrast is reduced.
Yes, but decreasing contrast is an unfortunate side effect, not the goal. This is like saying that the purpose of a light bulb is to increase your electricity bill.
> Dark themes (excluding amoled themes) exist to reduce the perceived contrast between the screen and the environment.
Yes, but not the contrast between text and background.
font-weight: 300, color: #555
nightmare that we see everywhere on the modern web.So lets just not.
Also, a backlight-based screen is not the same thing as a newspaper, where you can easily increase contrast by improving your light source almost infinitely. I can always decrease my screen brightness quite a bit, but there is an upper limit of increasing it.
By maximising contrast, one is trading short-term legibility with long term legibility. The maximum amount of contrast is as problematic as almost no contrast. There is a maximum useable deviation to both ends. By approaching max contrast, it gets harder to read for longer periods, because your photoreceptors approaching exhaustion, creating an after image [1]. It may happen slow enough to go unnoticed for some periods but should be noticeable at the end of a day as eye strain.
When most displays blast intense white light in your face at normal settings, it's not a screen brightness issue, it's a content brightness issue. Solved with controls such as dark modes, reading modes and options for users to customise. Obviously a lot of users prefer the full contrast experience, but many don't. Providing user choice is best strategy.
It's certainly possible to cause them by "bleaching" photo-pigments, but this requires extremely bright light. Other mechanisms likely produce the after-effects you normally encounter, and even there, eye movements (large and small) should help counter-act them unless the stimulus is very large and bright.
I have no doubt that overly contrast-y web pages can cause eye strain, but it's usually not because they're exhausting photoreceptors.
I'd associate eyestrain with the muscles in the eye. Like you can give yourself eye-strain by quickly moving the focus from close to far-away a couple of times.
Meanwhile, after-images are a neurological artifact. They do not cause your eyes to change focus, and are not caused by the muscles in the eye.
Although extremely bright light may strain the eyes in the same way your eyes may be sore from contracting if you go outside on a bright summer day.
What I described earlier as exhaustion is buried in a process called visual cycle, which is a biochemical process. If enough photons of a given wavelength hitting special molecules of a part of your retina, these molecules run through a replenishing cycle after photon absorption to run through the same loop again and again. If light source is strong enough, the cycle is not adequate to account for the incoming mass of photons, essentially triggering temporary deactivation. The molecules responsible for colour vision register the inverse of the incoming wavelength, as in: the absence of all other wavelengths registered gets interpreted as the colour one sees. This essentially creates the yellow after image if one looks at an object with strong red and blue content.
This is a can of worms and there is more involved, even on the side of the emitter which is why there is measurement in watts per steradian going on but my knowledge ends here. Maybe a Biologist can chime in.
If I'm sitting on my laptop in daylight, outdoors or in a room with large windows, I'd really like to max out the contrast while reading. Later in the day, the "Night Light" feature that's built into Windows 11 will reduce the contrast and increase the color temperature towards a yellower hue. (In past years I used f.lux for this.)
This kind of adjustment is not something each website should try to do. It's a system-wide setting that needs to take into account e.g. local sunrise/sundown times, like Night Light does. (And on iPhones, there's a light sensor that takes care of this.)
Even if your scene were in the middle of the night you would still use your brightest white ("FFFFFF") for the least-dark moonlit areas. (Striking recent example is The Northman fighting in the caves.)
In that context I wonder if the motivation for recommending near-white and near-black, i.e. foregoing dynamic range for no intrinsic benefit, is for contrast against other things in the user's field of view e.g. large images, browser toolbars, popup notifications, etc.
and guess what, it's far easier and more pleasant to use all contrast available in color and tone it down with the brightness setting of the monitor, than not diong grays on grays and having to shade or crank up contrast in the monitor
No, ‘Maximum contrast everywhere’ given as a directive without consideration is not a solution and will increase the problem.
Consider things beyond HDR displays: At technology progresses, we will approach superbright display technologies which will surpass the dynamic range of the human visual system. Technically, these will be as bright as light bulbs and brighter and could be used as such. Going by that max brightness directive, we will all stare happily into a direct light source one day. Or one is happily busy dragging the brightness slider up and down the whole day, one at a time for every app and site. It won’t work. To solve this, we would need tone mapping at the latest pipeline stage, everywhere. And this will, of course, again reduce contrast, but this time, by design.
The other major problem is: by leaving it all to the users (all three dimensions of the now prevalent color model), one throws every standard out of the window. One website will send out 4000 nits, the next one 350. One display can handle it, the other cannot. Color shifts abundant. How should that be accounted for? Furthermore, your model makes it impossible to design for: this removes the visual target platform and puts legibility and qualitative design principles at the mercy of technological progress. So solve this with the tech available, there were several agreements made to specify calibration targets - which include brightness and contrast settings, aka gamma in more than one dimension.
In a perfect world, no screen would leave the factory without a built-in calibration device and an ambient light sensor.
One more problem, the constant intermixing of use cases while discussing HDR displays: not every use case needs an HDR treatment. It does not make any sense. The main problem HDR solves is that content creators are not forced to squeeze 10 pounds into an 6 pound bag anymore. And if your display supports this, you can benefit from the full color space the content creator wanted the observer to see. Which is totally nice for hundreds of use cases. However, staring at a pitch black font next to a white background which emits 20.000 cd/m^2 would be painful.
2. I especially considered calibration in my comment and others above yours.
No, it doesn’t ignore it. Your comment, however, does not go into any details I mentioned besides ‘you are wrong‘.
What is actually your argument?
Otherwise I loved this list as a lay person.
Regarding color palette, I really like the work of Kate Rose Morley: https://fosstodon.org/@kate/109348023789472321
> “Pure black looks unnatural on a screen, and pure white is too bright.“
Even though it looks “unnatural“ at least I can read it.
I have always put this down to designers having very high quality monitors with excellent contrast. Apple screens (laptop or desktop) particularly tend to show those low contrast things as more readable than for the rest of us.
It is a plague that seems to be less bad than it used to be. I think it's ok in principle but it should be quite subtle. Also, I think that full-black should generally be used for text, but you can get away with more on the background (look at HN for example!).
Please don't. Reducing contrast of text makes it harder to read. Even if you do it just a little bit, it still makes it a little bit harder to read. Worse, a lot of designers seem to get carried away with this and end up with gray-on-gray text that's impossible to read for anyone over the age of 30.
Plus it doesn't even look better. I guess this is subjective but I frequently open the devtools inspector to edit people's CSS to turn their near-black into black and their near-white into white, and every time I'm like "Wow, that looks so much better!"
Maybe I'm just a systems engineer with no sense of taste but I absolutely don't understand why anyone wants this.