News for hackers. Stuff that matters.
Re:Design Tip: Never Use Black (2012) by mrob on Saturday August 29, 2020 @10:09AM (#24316215)
Pure black is the correct color for text. Ink and paper manufacturers go to great lengths to make inks and papers with the darkest blacks and brightest whites, and there's no reason text on screen should be any different. Firefox's Reader View foolishly throws away contrast with gray text, but this can be fixed in chrome/userContent.css in the Firefox profile directory:

  @-moz-document url-prefix("about:reader") {
    body {
      background-color: #FFFFFF !important;
      color: #000000 !important;
    }
  }
toolkit.legacyUserProfileCustomizations.stylesheets needs to be set to true in about:config for recent versions of Firefox to load userContent.css

Some people complain about excessive brightness being hard on their eyes. They likely have their monitor brightness set too high. Most monitors can have their brightness set using DDC/CI (this sometimes needs to be enabled from the monitor's OSD). Most Linux distributions include "ddcutil". Install it and give the user who'll run it permissions to access I2C. In Debian, this can be accomplished by adding them to the i2c group.

Find out which I2C buses your monitors are attached too:

  ddcutil detect
Now you can change brightness from the command line:

  ddcutil --bus=6 setvcp 10 50
The first number after setvcp is the feature value to set. "10" is the standard feature value for brightness. The second number is the percentage brightness. I suggest picking values for low/medium/high brightness for each monitor, and binding a script that sets all them at once to the otherwise rarely used PrtScn/ScrLk/Pause keys. Presumably there is some way to do the same thing on other operating systems.
Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @11:17AM (#24316656)
There's a huge difference in having a surface that's white reflecting your room color versus having a display blasting light directly into your eyes.

Computer screens and paper are not comparable, they're physically different and they're not really even used in the same fashion. Yes, you can read off of both but you get the point.

You sound like a person who uses a terminal with a black bg and neon green text and claim that as superior. Maybe to you but surely not for the majority. Most likely that's not even optimal for you but you've just convinced yourself of that.

I get the frustration you seem to carry towards designers, but if you're blaming _all_ designers because some might utilize anti-patterns or you just have personal preferences that differ, you're kinda missing the woods for the trees.

You do realize that the chair you're sitting on, device you're writing on and building you're (likely) in are all designed by designers.

Re:Design Tip: Never Use Black (2012) by tzs on Saturday August 29, 2020 @12:41PM (#24317337)
> There's a huge difference in having a surface that's white reflecting your room color versus having a display blasting light directly into your eyes.

What's actually different between a photon of a given frequency that enters my eye after reflecting off a surface and a photon of the same frequency that enters my eye after being emitted from a display?

> You sound like a person who uses a terminal with a black bg and neon green text and claim that as superior. Maybe to you but surely not for the majority

BTW, in the CRT days green on black was actually objectively superior if you were using small fonts on most displays. That was because most displays would have slight misalignment of the red, green, and blue, especially near the edges, leading to color fringing around white things. For small text, the fringing could make text blurry and hard to read.

Pure green on black had no red or blue, so no fringing. Red on black or blue on black would have worked too, but most people find those much harder to read than green on black.

Re:Design Tip: Never Use Black (2012) by ChuckNorris89 on Saturday August 29, 2020 @01:34PM (#24317817)
Because the light emitted from the LEDs of the display is focused towards your eyes by a very reflective film behind the panel while the light reflected off a book's page is heavily diffused due to the roughness of the paper.
Re:Design Tip: Never Use Black (2012) by jml7c5 on Wednesday September 02, 2020 @02:22AM (#24350548)
The photons are not somehow "different" because of this.
Re:Design Tip: Never Use Black (2012) by dragonwriter on Saturday August 29, 2020 @07:13PM (#24320077)
> What's actually different between a photon of a given frequency that enters my eye after reflecting off a surface and a photon of the same frequency that enters my eye after being emitted from a display?

Nothing.

OTOH, the spectrum of photons emitted from maximally white and maximally black pixels on an LCD screen is probably nothing like those reflected from black ink or bright white paper under any realistic lighting conditions.

Re:Design Tip: Never Use Black (2012) by guenthert on Saturday August 29, 2020 @01:57PM (#24318064)
But "your room color" is not the same frequency as "display blasting light". The former will vary with time of day (some displays try to mimic that now).
Re:Design Tip: Never Use Black (2012) by mixmastamyk on Saturday August 29, 2020 @07:34PM (#24320161)
I preferred amber monochrome, the ergonomic choice. Especially at night time.
Re:Design Tip: Never Use Black (2012) by PowerBar on Saturday August 29, 2020 @06:21PM (#24319825)
Reading black text on a pure white computer screen capable of a decent contast ratio is more akin reading black text on tin foil with a studio light behind you.
Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @09:43PM (#24320671)
Yes, you are of course right, technical limitations have had reasons in the past to use suboptimal solutions if we're talking about coloured pixels in CRT or LCD displays even but in today's world with our display technology there's no real reasons to use those other than personal preference.

About the photons, you could look into a regular paper sheet's or book page paper's albedo values and compare that to the light emitted from a led display, it's not even in the same ballpark. Why do you think people enjoy reading on an ebook reader rather than a normal tablet with a lcd/led display?

Artificial light strains our eyes way more than normal sunlight (or even indoor lighting) reflecting off of surfaces indirectly lighting everything for us.

Re:Design Tip: Never Use Black (2012) by simondw on Saturday August 29, 2020 @06:50PM (#24319973)
> What's actually different between a photon of a given frequency

Well, none, of course. But the point is that white paper and a display's #FFFFFF probably won't send the same wavelength or number of photons into your eye.

Re:Design Tip: Never Use Black (2012) by Kaze404 on Saturday August 29, 2020 @01:45PM (#24317926)
> What's actually different between a photon of a given frequency that enters my eye after reflecting off a surface and a photon of the same frequency that enters my eye after being emitted from a display?

One of them gives me a migraine after 5 minutes. I assume because light being reflected off a sheet of paper gets weaker, though I'm not sure how.

Re:Design Tip: Never Use Black (2012) by dathinab on Saturday August 29, 2020 @08:13PM (#24320335)
I think I have the right to blame them for creating accessibility nightmare which are unreadable without modifying CSS for many people while claiming it's a good helpful thing.

> You do realize that the chair you're sitting on, device you're writing on and building you're (likely) in are all designed by designers.

ANY designer having gone through design school can tell you that low contrast text is a no-non.

So maybe we should just say that the people doing designer jobs without learning about the basics of color, contrast and accessibility are unqualified to do their job in the same way a architect is unqualified if they design streets to small for cars or similar.

Btw. if you have problems with to bright whites (which I increasingly feel is related to OLEDS but that's just a wield guss). Make the background non-white but keep the text black or very close to black.

Also just to be clear I think no on is blaming all designers but just such which do thinks like gray on gray. And then believe it's all okay because their expensive OLED display displays it still kinda readable (again I'm just guessing about OLEDS, I think I have to make sure to get my hands on one to check that).

Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @10:00PM (#24320745)
I didn't talk about low contrast at all, I specifically mentioned WCAG2.1 as it has set minimum contrast values for certain text sizes which should be readable. I forced my previous place of employment to take WCAG AA-level as a minimum for every UI element and created a separate high contrast mode for our product which fulfilled the AAA-levels even though we weren't legally obligated nor had any customer ever asked for it.

In the example (yellow on black) I mentioned has too much contrast and actually hinders readability for most people with a normal visual acuity as well as certain types of impairments.

Designers are also the ones responsible _for_ all the accessibility features and standards set to help developers implement accessible solutions.

If you're a software engineer who cares about contrast and studies different vision problems to figure out solutions for example, you're a designer in my book.

This is why I also specifically separated aesthetic and usable design. The former is more akin to "art" as it aims to simply look nice and I don't personally consider it design as design is problem solving and bad design just creates more.

I've always said that if a designer or web developer doesn't actively hinder accessibility, it's already a win in my book. It requires someone to make the decision to slap a #fafafa shaded text o top of a #ffffff background, semantic html and OS default colors go a long way if you don't know better.

Re:Design Tip: Never Use Black (2012) by an_opabinia on Saturday August 29, 2020 @10:44AM (#24316434)
You'd have a really interesting conversation with an artist or designer if you asked, "What is the correct color for text?" instead of uh, just saying that the answer is whatever your computer draws as RGB #000.

That's part of what this article gives you, why it's talking about art school and not technology. Miscommunication - incommensurability of how to see the world really - is the pitfall when engineers are tasked with creating a subjective thing and asked to try to do something simultaneously functional, familiar and original.

Just put yourself in this guys shoes. Just like you are excited to share Linux display color control commands, this guy is excited to share a new way of thinking about black and dark shades that instantly expands your vocabulary - both for creating new things and understanding the decisions of others.

Anyway, the negativity of others in this thread, it's ironic because that's exactly the point of the article, really, that the pedantry gets in the way of being creative - or at the very least, seeing things originally.

I work with an artist daily. I appreciate and value his opinions that there should be no pure black in the creative product we make together. It elevates what we make above all our competitors. It's an extremely insightful perspective.

Re:Design Tip: Never Use Black (2012) by mrob on Saturday August 29, 2020 @10:48AM (#24316463)
I don't see why I should care about the opinion of designers when they're the ones responsible for such anti-features as vanishing scrollbars and hamburger menus. RGB #000 isn't truly black, but it's always the best approximation of black available on a computer monitor.
Re:Design Tip: Never Use Black (2012) by gnulinux on Saturday August 29, 2020 @01:37PM (#24317845)
What's wrong with vanishing scrollbar? I prefer them this way. The first thing my emacs config file does is to hide scrollbar.
Re:Design Tip: Never Use Black (2012) by mrob on Saturday August 29, 2020 @04:14PM (#24319096)
It makes me waste valuable working memory remembering my position in the document, and the animation of it appearing and disappearing is distracting. I have a widescreen monitor so I have plenty of horizontal space already.
Re:Design Tip: Never Use Black (2012) by nwienert on Saturday August 29, 2020 @07:20PM (#24320108)
Even though I agree with you re: pure black text, I sense a lack of understanding that should be present here.

Design is always a trade off. Do you want more focus on content, or more information with less focus? Is your default setting more friendly to smaller or larger screens? Every person has different preferences, and every trade off has cost benefits you can run. Yet your statement here is very “black and white” (ahem), assuming everyone should think like you. That betrays a lack of nuance in understanding how design works.

In the programming world, you also have these trade offs, yet it’s easier to avoid thinking about them at times. Static vs dynamic languages are full of trade offs like this.

To avoid coming across as yelling at clouds, attempt to frame why it’s a trade off you prefer, rather than a platonic ideal others don’t see (because it isn’t).

Re:Design Tip: Never Use Black (2012) by ryukafalz on Saturday August 29, 2020 @01:53PM (#24318018)
Mine too, but I’m already familiar enough with Emacs that I don’t need it, and in general most things in Emacs are scrollable and you can recognize them as such once you’ve used it for a while.

It would not be the right choice for a default config, or in a context where sometimes things are scrollable and sometimes they aren’t. (This is often the case on mobile phones; if there’s no scroll bar, the only way to tell if something is scrollable is to try it, if you think to.)

Re:Design Tip: Never Use Black (2012) by sporkologist on Saturday August 29, 2020 @03:49PM (#24318911)
It adds to cognitive load, now I have to hunt for the frickin scrollbar... mystery-meat UI if you ask me.
Re:Design Tip: Never Use Black (2012) by robocat on Saturday August 29, 2020 @04:18PM (#24319127)
Discussion from two days ago: https://news.ycombinator.com/item?id=24293421
Re:Design Tip: Never Use Black (2012) by BurningFrog on Saturday August 29, 2020 @11:17AM (#24316651)
To be fair, we engineers also have plenty of UI war crimes to answer for :)
Re:Design Tip: Never Use Black (2012) by kbutler on Saturday August 29, 2020 @11:51AM (#24316918)
But do we claim to be the experts, authorities, and judges of UI design?

Well, ok, sometimes we do, but...yeah.

Re:Design Tip: Never Use Black (2012) by tingol on Saturday August 29, 2020 @12:40PM (#24317333)
The smarter ones usually iterate based on user input.
Re:Design Tip: Never Use Black (2012) by a1369209993 on Saturday August 29, 2020 @02:13PM (#24318180)
To be fair, the smarter designers do too, but you don't hear about them because good design doesn't shove itself in your proverbial or literal face.
Re:Design Tip: Never Use Black (2012) by notatoad on Saturday August 29, 2020 @03:36PM (#24318835)
and some of the designs that you don't personally like were undoubtedly the result of iterating based on user input - what actually tests well with users is very often not what the sort of people who post on hacker news would assume is the best design.
Re:Design Tip: Never Use Black (2012) by IggleSniggle on Sunday August 30, 2020 @12:42PM (#24323960)
Yeah, just to add:

and some designs come out of relentless targeting the impact of the bottom line at the expense of aesthetic or "pleasurable to use", some designs come out of snake-oil sales-people, etc etc.

Different populations, different needs/wants/desires/cultural expectations. This is what focused advertising is all about. You can create one interface and say "everyone must use and learn to love this one," and that can work well. You can also gain immediate appeal by creating "one interface for each population of potential users" and relentlessly target your designs for each of those populations. I don't think we've fully recognized it in software engineering circles, but I think a lot of what are producing today is really about creating different experiences for different populations when the core capabilities have been there, available for free or on extremely cheap computing platforms, for anyone to use, for decades.

I imagine that's fundamentally what the job of most software engineers is today: find the design that best matches the needs of the customer, and build a workflow for their needs.

Re:Design Tip: Never Use Black (2012) by Kaze404 on Saturday August 29, 2020 @01:46PM (#24317951)
Not just UI crimes either. I know of at least one that lost a company a couple hundred thousand due to clever engineering.
Re:Design Tip: Never Use Black (2012) by baddox on Saturday August 29, 2020 @12:18PM (#24317160)
You’re asking why you should care about opinions that are different than your opinions?
Re:Design Tip: Never Use Black (2012) by yowlingcat on Saturday August 29, 2020 @11:27AM (#24316736)
There's no need to care about their opinions, but what's being talked about here is not opinion. They're basic principles of color theory that have remain unchanged for centuries if not millennia. They became principles because they work. What do you think is more likely to be incorrect -- the millennia old principles, or your unsubstantiated, untrained opinion?

I agree with your chagrin for vanishing scrollbars and hamburger menus, by the way. There ought to be a good term for designers who do the opposite of what good design does (which is make things which are usable).

Re:Design Tip: Never Use Black (2012) by msla on Saturday August 29, 2020 @10:55AM (#24316513)
> I appreciate and value his opinions that there should be no pure black in the creative product we make together.

Is this why the most fashionable websites are also the most difficult to read? I ask purely for information.

Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @11:22AM (#24316686)
Aesthetic design and usable design are very different things. If the sites you're talking about are made by people who care more about making things look nice instead of being usable, then yeah that would be the issue.

WCAG2.1 has some great guidelines when it comes to color contrast in digital text and as long as those are adhered to, most people will have a near optimal experience consuming that text.

And yes, too big of a contrast difference is not great either. Just try to throw bright yellow on top of a black background, it's gonna hurt your eyes pretty quick.

Re:Design Tip: Never Use Black (2012) by an_opabinia on Saturday August 29, 2020 @11:00AM (#24316530)
Instagram's text color, the first but not the last I'll check, is "rgb(38, 38, 38)." I wouldn't characterize it harder to read than this website, which uses "rgb(0, 0, 0)", or easier to read than the NYTimes (the third), which uses "rgb(85, 85, 85)." Anyway, I would hardly characterize those as fashionable, they are some of the portals on the Internet. So maybe you're talking about a different site, or something, but certainly, among the most mainstream sites, there is a consensus to not use pure black in the font.
Re:Design Tip: Never Use Black (2012) by chrismorgan on Saturday August 29, 2020 @11:26AM (#24316728)
Windows distressingly has two completely different mechanisms and APIs for setting brightness: one that operates over DDC/CI, and another that does something else (I’ll call it Method B, not knowing a better name). External monitors use DDC/CI, internal monitors (mostly meaning laptop screens) use Method B. I have failed in any attempts to hook brightness keys in user space (like how on Linux you’d just intercept XF86BrightnessUp and XF86BrightnessDown); something steals those keys before they ever get to user space, and use Method B. And there is no user interface anywhere for DDC/CI adjustment: it’s only an API that you can call.

So the end result is that Windows users can’t adjust the brightness of their non-laptop monitors without third-party software, or reaching around the side of the screen and fiddling with the infuriating controls of the frustrating OSD interface. So almost no one ever adjusts their screen’s brightness at all, and almost no one of the remainder adjust their screen’s brightness to match conditions. And manufacturers have (understandably) decided that too dim is worse than too bright. So most people’s screens are genuinely painfully bright. So then people say “don’t use actual white” and “don’t use actual black”. And those that have calibrated displays end up sad.

Re:Design Tip: Never Use Black (2012) by jimmyspice on Saturday August 29, 2020 @04:22PM (#24319150)
hey, try ClickMonitorDDC: https://clickmonitorddc.bplaced.net/

It allows you to change brightness, contrast (and volume, never tried it), from the taskbar.

It works for a Dell and iiyama monitor I own, but not my Agon one, so YMMV

Re:Design Tip: Never Use Black (2012) by chrismorgan on Saturday August 29, 2020 @05:57PM (#24319706)
I found a freeware program ScreenBright a few years back and use it so that I type “b 0” in my command line to set the brightness to zero. (I tried it out to confirm that this DDC/CI thing would actually work, before I bothered delving into the Windows APIs to write my own CLI; but then figured, since it had a CLI, why bother? and just wrote a batch file around it that contains `@%~dp0\screenbright.exe -set brightness %1 -set screen 2 -set brightness %1` to do both monitors at once.)
Re:Design Tip: Never Use Black (2012) by robocat on Saturday August 29, 2020 @04:22PM (#24319156)
> something steals those keys before they ever get to user space

The brightness keys could be managed by BIOS? If you can modify brightness during early boot, or while BIOS settings is showing, then there is a chance Windows doesn’t see those keypresses.

Re:Design Tip: Never Use Black (2012) by chrismorgan on Saturday August 29, 2020 @06:08PM (#24319763)
No, they’re being handled from within Windows, somehow—it shows a screen brightness adjustment popup thingy in the corner, same as it does if you adjust the volume by key. I think it must just be some driver or something consuming them and turning them into something else.

I do wish I could intercept it, not just for external monitors’ sake, but also so I could make it logarithmic or similar, like I did in Arch Linux + i3 with XF86Brightness{Up,Down} mapping and an xbacklight wrapper script. On my Surface Book, the smallest effective brightness change is 2%, and each 2% step between 0% and about 20% has at least as much effect as 40–50% or 80–100%, yet the seemingly-hardcoded behaviour is that the brightness keys just adjust the level by a flat 10%, which is what every platform does (OK, I can actually only directly attest to Android, Ubuntu from some years ago, xbacklight by convention and Windows, but I think the rest do it to), even though such a linear scale is obviously stupid and wrong. On my phone, two millimetres of adjustment on the left has about as much effect as the whole right hand side of the scale (several centimetres).

Re:Design Tip: Never Use Black (2012) by FpUser on Saturday August 29, 2020 @11:48AM (#24316901)
>"So the end result is that Windows users can’t adjust the brightness of their non-laptop monitors without third-party software"

Not sure what are you talking about. I can adjust brightness (and lots of other things) of my monitors just fine using their own buttons.What on Earth does that have to do with the Windows OS?

Re:Design Tip: Never Use Black (2012) by chrismorgan on Saturday August 29, 2020 @12:06PM (#24317063)
Please finish reading the sentence you’re quoting.
Re:Design Tip: Never Use Black (2012) by FpUser on Saturday August 29, 2020 @02:53PM (#24318520)
Yeah, guilty. Still not sure if it practically matters. Do they really need to adjust brightness every day?
Re:Design Tip: Never Use Black (2012) by chrismorgan on Saturday August 29, 2020 @06:10PM (#24319775)
If you’re in a windowless or heavily-shaded office with consistent lighting, probably not.

But if you’re in a normal house in a room that gets plenty of lighting from outside, absolutely. I tend to run my external monitors at 0% in the earlier morning, 20% in the mid-morning, 40% by the afternoon, sometimes up to 70% on a particularly bright summer day, and down to 0% in the evening (and I’d take it towards −20% at times if there was such a thing, their minimum brightness is nowhere near as dim as my laptop’s screen’s minimum brightness, which is even acceptable for use in a completely dark room; their 0% is its 25%, while their 100%s are similar). Leaving them at the 100% they came at would be awful, it’s a little too bright for my situation even in the middle of the day, let alone the evening.

Re:Design Tip: Never Use Black (2012) by FpUser on Saturday August 29, 2020 @08:44PM (#24320445)
>"If you’re in a windowless ..."

Yup. That would be me. My office is in a basement of my house and has been for the last 20 years.

Re:Design Tip: Never Use Black (2012) by mrob on Saturday August 29, 2020 @04:20PM (#24319139)
The appropriate brightness for programming or browsing the web isn't the same as for gaming or watching movies. Samsung monitors have a dedicated button for cycling through brightness profiles. DDC/CI control is even better.
Re:Design Tip: Never Use Black (2012) by jhardy54 on Saturday August 29, 2020 @10:40AM (#24316418)
> Pure black is the correct color for text. Ink and paper manufacturers go to great lengths to make inks and papers with the darkest blacks and brightest whites, and there's no reason text on screen should be any different.

Is this your opinion or is this widely accepted as fact? I've read countless design suggestions to reduce contrast and avoid using pure black or white on an LED display. I'm curious whether there's research that supports either side.

Re:Design Tip: Never Use Black (2012) by bmitc on Saturday August 29, 2020 @02:07PM (#24318137)
> I've read countless design suggestions to reduce contrast and avoid using pure black or white on an LED display.

I have seen those suggestions too, but they seem to be just parroted off of each other. I have never seen a single one link to any reasoning or studies that support the claims of better readability. They all seem to say it because someone else said it in a game of design telephone.

In my personal experience, I find gray text on an off-white background to be very difficult and straining to read, and additionally, I don't think it looks good.

I can see some merit in reducing the whiteness and thus brightness of the background, but I don't see why reducing black to some lighter black or gray helps at all. Having text in a nice solid black or near-black with an off-white background seems reasonable to me. That matches more closely with reading things on actual paper, where dark black inks are possible but the background is not pure white. That leaves legibility in place and reduces background brightness.

It's possible this whole "reduce the contrast" thing has gotten off track, when to me at least, the goal seems to be to reduce the blinding background blasting you with light and not to simply reduce contrast.

Re:Design Tip: Never Use Black (2012) by unicornporn on Saturday August 29, 2020 @04:37PM (#24319250)
> I have seen those suggestions too, but they seem to be just parroted off of each other. I have never seen a single one link to any reasoning or studies that support the claims of better readability. They all seem to say it because someone else said it in a game of design telephone.

I so wish I could find that research that once and for all debunked the "UX expert" urban myth that #fff + #000 = evil. It made me consider past mistakes and I go for all black on all white whenever I can. Doesn't hurt from a WCAG perspective.

Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @10:12PM (#24320796)
I debunk your debunk with the following paper.

Rello, Kanvinde, & Baeza-Yates, 2011. Layout Guidelines for Web Text and a Web Service to Improve Accessibility for Dyslexics.

If you suffer from astigmatism you might experience halations or if you have contrast sensitivity, visual distortions.

https://dm-ed.com/info/contrast-sensitivity/

Re:Design Tip: Never Use Black (2012) by amelius on Saturday August 29, 2020 @11:46AM (#24316886)
> Is this your opinion or is this widely accepted as fact?

Well, in either case, perhaps nobody should hard-code the darkness of text in their CSS but instead allow the user to set it in their browser?

Re:Design Tip: Never Use Black (2012) by jhardy54 on Saturday August 29, 2020 @08:19PM (#24320350)
Unfortunately browsers have lots of objectively bad defaults (e.g. h1 { font-size: 200%; }) so we have to decide which defaults we should fix and which ones we should leave alone.

I agree that the user should have browser defaults that they prefer, but motherfuckingwebsite.com still looks awful in most browsers.

Re:Design Tip: Never Use Black (2012) by httpsterio on Sunday August 30, 2020 @10:21AM (#24323171)
it might be ugly, but it's easy to consume and the experience is way better than on "well designed" sites with user hostile design choices
Re:Design Tip: Never Use Black (2012) by FpUser on Saturday August 29, 2020 @11:53AM (#24316937)
>" I've read countless design suggestions to reduce contrast and avoid using pure black"

>"I've read countless design suggestions to reduce contrast" I would say that modern design suggestion often the opposite of usability/ergonomics. On many sites you now often see undecipherable light grey text on white background. It sure is soothing. It also sure is useless as many people who do not have perfect vision are unable to actually read it without blowing text size out of proportion.

Re:Design Tip: Never Use Black (2012) by formerly_proven on Saturday August 29, 2020 @12:03PM (#24317036)
Fortunately ultra-light (sub-pixel stroke width) grey fonts on grey backgrounds as a design trend has been receding again. Rule of thumb: The lighter the font, the bigger the face needs to be! Ultra-light is okay for a hero text that's literally 100 pixels tall, but never for body text.
Re:Design Tip: Never Use Black (2012) by criddell on Saturday August 29, 2020 @06:51PM (#24319977)
Yeah, I don't buy it either. Books can be printed on anything a publisher wants, yet most books use a creamy paper rather than the whitest white they can get.
Re:Design Tip: Never Use Black (2012) by rejap on Saturday August 29, 2020 @06:56PM (#24319998)
here is something with a link to a research. The examples used in article convinced me to avoid pure white and black.

https://uxmovement.com/content/why-you-should-never-use-pure...

Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @10:15PM (#24320813)
Tony and UX Movement is chock full of bad advice, doesn't do proper research and can't take criticism at all. I would avoid it at all costs. Feel free to read his "article" "The Aesthetic-Accessibility Paradox" and "Why radio buttons and checkboxes can't coexist" and read the comments to those and see what I mean.
Re:Design Tip: Never Use Black (2012) by im3w1l on Saturday August 29, 2020 @11:24AM (#24316707)
I think a parallel can be drawn to the loudness wars in music.

The user can easily change brightness of their screen just as the user can easily change volume of their music. But producers want their creation to stand out. Make their music a little bit louder, or their website a little bit softer than the rest.

In both cases the outcome is a race to the bottom and reduced dynamic range.

And finally, in both cases it's fairly inconsequential. Things get worse but only a little bit.

Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @11:28AM (#24316743)
OP's comment sounds to me like they want to throw a compressor with a low threshold and high gain on top of their master and gave everything either clipping or gated. Screw transients, am I right?
Re:Design Tip: Never Use Black (2012) by mrob on Saturday August 29, 2020 @12:02PM (#24317029)
Text is not music. Transients don't belong in text.
Re:Design Tip: Never Use Black (2012) by httpsterio on Saturday August 29, 2020 @10:18PM (#24320829)
I don't enjoy staring directly at the sun as I do not enjoy sitting with my ear pressed against the speaker at a festival. Your senses are not meant to be either not stimulated at all to fully stimulated, there is such a thing as a sane middle ground.

Please do some research instead of doubling down on opinions you're presenting as absolutes.

Re:Design Tip: Never Use Black (2012) by chrismorgan on Saturday August 29, 2020 @11:32AM (#24316780)
> The user can easily change brightness of their screen just as the user can easily change volume of their music.

This is just not true.

100% (minus rounding error) of devices can easily adjust volume.

Phones and laptops can adjust brightness, but dodgy automatic brightness adjustment is the rule of the day. And basically no desktop monitors can easily adjust brightness (not because they can’t, but because OSes have frustratingly ignored functionality that has been standard for a decade or two; on-screen brightness adjustment is absolutely consistently painful enough to use that I disqualify it for the word “easily”—oh for the brightness wheels of the CRTs of yesteryear!).

Re:Design Tip: Never Use Black (2012) by hammock on Saturday August 29, 2020 @08:19PM (#24320351)
>Ink and paper manufacturers go to great lengths to make inks and papers with the darkest blacks and brightest whites

That this is the top comment and yet no one has refuted it boggles me. I cannot think of anything I've read recently that uses bright white paper. Sometimes I see reams of bright white paper for sale for a few extra $. However if I'm printing a resume, it's on x% linen slightly off white. If I'm reading a book, it's on warm-colored paper. If I'm reading music, it's on even warmer colored paper- and dare I say it as a musician for decades, the stuff on bright white paper (a photocopy, or self-published octavo for example) is the HARDEST to read!

Re:Design Tip: Never Use Black (2012) by cma on Saturday August 29, 2020 @09:39PM (#24320658)
Even hacker news itself is black on a warm paper color
Re:Design Tip: Never Use Black (2012) by kps on Saturday August 29, 2020 @10:43AM (#24316431)
For monitors, http://www.lagom.nl/lcd-test/ is helpful for making adjustments without external calibration tools.

For books, paper isn't the brightest white; it's only copy/printer paper that got in to a ‘horsepower race’ for brightness.

Re:Design Tip: Never Use Black (2012) by userbinator on Saturday August 29, 2020 @06:46PM (#24319949)
Some people complain about excessive brightness being hard on their eyes. They likely have their monitor brightness set too high.

This, absolutely! Monitors usually come with an eye-searingly-bright default that's meant to look good in a showroom and wear out the backlight more quickly, not at all a good brightness/contrast for normal use. I set my monitors to 0 when they were new, and that was already very bright; now, many years later, they've gone up to 20-40 to compensate for backlight degradation, but are otherwise still more than bright enough.

Re:Design Tip: Never Use Black (2012) by nabilhat on Saturday August 29, 2020 @01:41PM (#24317880)
The majority of text displayed on a monitor only uses a small number of pixels, which emphasizes the edges where it doesn't cleanly intersect all of the component colors of the white background. #000 on #FFF emphasizes the colorful artifacts. We don't control what monitors our users own. Taking a step away from the most extreme possible contrast makes our UI's look a lot less like rainbow bleeding failure on the uncalibrated 1080p 29" monitors commonly used by executives making software expense decisions.
Re:Design Tip: Never Use Black (2012) by gibolt on Saturday August 29, 2020 @11:59AM (#24316996)
Looking to have easy control of monitor brightness?

For Mac users, look at https://lunar.fyi/. There are a bunch of other options as well.

For Windows, look at https://github.com/emoacht/Monitorian

Re:Design Tip: Never Use Black (2012) by 0134340 on Saturday August 29, 2020 @01:50PM (#24317979)
Wow, just today I learned I can control my monitor via software and it worked. All this time I've just dealt with the brightness since I game on it and use dark themes to mitigate the white flashing. Besides that it takes a while to adjust and my monitor's on a flimsy mount and so I hate to have to move touch it. I'm going to hotkey it and have a one-button solution now. Thanks to your comment and to OP's.
Re:Design Tip: Never Use Black (2012) by limomium on Saturday August 29, 2020 @10:40AM (#24316411)
There are multiple blatantly obvious reasons why text on screen SHOULD be different. For one, IT'S NOT PAPER. Second, you should avoid blasting unnecessary light into your users' eyes. Third, bright screens consume more power than dark ones.
Re:Design Tip: Never Use Black (2012) by tinus_hn on Saturday August 29, 2020 @10:50AM (#24316475)
Only if they are CRTs or OLED screens, both a distant minority.

No need to yell.

Re:Design Tip: Never Use Black (2012) by saaaaaam on Sunday August 30, 2020 @05:04PM (#24325934)
Many years back, at the cusp of consumer internet taking off I owned a magazine company - we worked purely in print.

Pure black is often not the correct colour for text, unless it’s monokrome (“B&W”) printing, rather than CMYK (but more on that later, because B&W monokrome black is often not “true black” either).

If you are printing CMYK you rarely use key (“K” - black) on its own, but rather use a CMYK mix to build a black shade, to give a rich black (more M) or cooler black (more C) or balanced black - neutral but not stark. The different mix can really change the way a page feels - and the right mix on the right paper (“stock”) can make the black pop or muddy, and have a huge impact on readability. This is really important when you’re designing for print. It really does make the difference between someone continuing to read and chucking your print aside after a paragraph. Good print designers know how to build different blacks for different stock.

When you are printing in monokrome black you are really printing g a shade of grey, to a greater or lesser extent, determined by the absorbency of the paper you are printing on.

And, indeed, different inks have different qualities so some “black” ink for monokrome print maybe be built from various pigments giving it a slight blue sheen or a brownish tint under certain lights. Plus inks - and the paper substrate - are more or less reflective meaning they will behave and appear differently depending on the light conditions.

I loved working in print.

Re:Design Tip: Never Use Black (2012) by hellotomyrars on Saturday August 29, 2020 @06:57PM (#24320009)
I have a very high sensitivity to light as a side-effect of medication.

Dark/black background with lighter text doesn’t bother me. White background with black text does.

Are you really going to tell me that I’m wrong for doing what is right for me because of your opinion?

The monitor only goes so low. And this works. Paper is very different to a screen. There’s a reason e-readers exist.

Maybe people should just do whatever they prefer/works better for them instead of insisting that light themes or dark themes are objectively better.

Re:Design Tip: Never Use Black (2012) by kitsunesoba on Saturday August 29, 2020 @04:01PM (#24318991)
The frustrating thing about lowering brightness is that on a great number (probably the majority) of computer displays, lower brightness comes with lower contrast and color vibrance as a side effect of the pixels and backlight being separate layers in traditional LCDs.

Because of this, for me the biggest benefit of upgrading to a phone with an OLED display was that it enabled me to adjust my phone's brightness without such dramatic loss of contrast and vibrance. Unfortunately I don't think OLED panels will ever become practical for desktop monitors… they're just now becoming somewhat available in laptops and even then sometimes come with issues similar to those seen in early OLED phone screens. We're probably going to have to wait for microLED tech to mature to get this benefit in full sized monitors.

Re:Design Tip: Never Use Black (2012) by morsch on Saturday August 29, 2020 @04:41PM (#24319275)
Why not? Large, high res OLED TVs are common (if expensive). Burn-in?
Re:Design Tip: Never Use Black (2012) by kitsunesoba on Saturday August 29, 2020 @04:58PM (#24319390)
I'm not part of the industry or well-read on it so I can't well explain why, but if I had to guess this is due to the dramatically smaller volumes involved.

There's far fewer desktop monitors and laptops being shipped than phones or TVs, and the majority of desktop and laptop panel sales are tied up in basic office-grade econoscreens and gaming monitors focused on high refresh rates and low input latency. Midrange/affordable laptop/desktop OLED panels fit neither of these categories and as such haven't received nearly as much investment and R&D.

Re:Design Tip: Never Use Black (2012) by 0-_-0 on Saturday August 29, 2020 @10:25AM (#24316320)
To find your profile directory, go to about:support

To only apply the tweak to the dark theme, you can do:

    @-moz-document url-prefix("about:reader") {
      body.dark {
        color: #FFFFFF  !important;
        background-color: #000000 !important;
      }
    }
Re:Design Tip: Never Use Black (2012) by dathinab on Saturday August 29, 2020 @08:05PM (#24320292)
> brightest whites

I which they would not, it's annoying when reading outside.

But I'm all in for the darkest blacks.

And yes I agree that if the contrast is to bright it most times you monitor which is generally set to bright.

Hm, maybe one exception might be OLED screens, but reducing the general screen brightness should still work.

If you are still convinced that it's to bright DO NOT make the black not black but make the withe less bright, preferable some subtle bright non gray color like for example hacker news does it.

That makes the contrast less strong without being a accessibility nightmare which requires people to open their web-console and modify your CSS.