You want enabling CSS selectors, not disabling ones

Re:You want enabling CSS selectors, not disabling ones by leephillips on Tuesday August 31, 2021 @07:47PM (#28374981)

That site is black on white¹, and has no other colors, images, fancy borders, nor any other obvious “design”—and yet it is remarkably pleasant to look at, even beautiful. The site sells the authors’ ideas; they obviously know something. (Plus no doorslams, cookie warnings, or other annoyances. And an RSS feed.)

[1] Really very dark grey on very light grey.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by juped on Tuesday August 31, 2021 @09:48PM (#28375682)

"and yet"? It's "and therefore".

† The only problem is that the atrocious #fafafa on #050505 is made a whole lot worse because there aren't a bunch of even worse things distracting you from it.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by chipotle_coyote on Tuesday August 31, 2021 @10:07PM (#28375764)

Okay, I'll bite. Why is #050505 on #FAFAFA (not the reverse, as you stated) "atrocious"? Are we playing the "anything less than #000000 on #FFFFFF is grey text on a grey background and entirely unreadable" card?

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by extra88 on Tuesday August 31, 2021 @10:58PM (#28376044)

I don't understand their complaint either. Some people have a hard time with absolute black on absolute white (and/or vice versa) so easing up a little can be helpful. It's a small difference, 19:52:1 vs. 21:1 contrast ratio. I've seen advice to avoid exceeding 18:1 in large areas, maybe #111 on #f9f9f9.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by chipotle_coyote on Wednesday September 01, 2021 @02:28AM (#28376951)

We tend to focus only on the accessibility issues caused by low contrast, but very high contrast also makes reading more difficult, especially for people with dyslexia -- and it's also more likely to cause eye strain if it's a full-length article.

At any rate, "it's okay for text not to be pure black and backgrounds not to be pure white" has become my tiny hill to die on.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by extra88 on Wednesday September 01, 2021 @08:03AM (#28378761)

Maybe browsers should go back to using a gray background by default, but less gray than one Mosaic and the other used.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by dotancohen on Wednesday September 01, 2021 @02:02AM (#28376827)

How do you calculate the contrast ratio?

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by chipotle_coyote on Wednesday September 01, 2021 @02:39AM (#28377010)

I use the WebAIM contrast checker:

https://webaim.org/resources/contrastchecker/

It's basically a measure of perceived brightness. The actual formula involves calculating the relative luminance of the background and foreground colors, where luminance is a value from 0 (darkest) to 1 (lightest), and using the formula

(lighter_luminance + 0.05) / (darker_luminance + 0.05)

So the highest possible contrast ratio in this system is 21:1.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by dotancohen on Wednesday September 01, 2021 @06:27AM (#28378140)

I see, thank you.

[ Parent | on HN ]

Re:You want enabling CSS selectors, not disabling ones by extra88 on Wednesday September 01, 2021 @07:57AM (#28378693)

The WebAIM contrast checker web page is one of many. It's nice because the colors have lightness sliders so one can quickly try alternatives then copy the hex values into your CSS.

I like checking with Lea Verou's https://contrast-ratio.com because it can check colors written in many different formats, not just hex. Also, it can do +/- contrast ranges when colors include the alpha channel.

In the Chrome and Firefox DevTools, you often can simply click the color swatch for the `color` property. The pop-up includes the contrast number vs. the background-color for that text and whether or not it meets a Web Content Accessibility Guidelines (WCAG) contrast criteria (Level AA if it's 4.5 or above for regular-sized text, Level AAA if its 7 or above for regular-sized text).

[ Parent | on HN ]