When I was a kid, various art teachers taught me about The Color Wheel with its Three Primary Colors and its Three Secondary Colors and while that wheel did help me make greenish paint when the classroom only had yellow and blue, it also gave me some wrong ideas about color.

"Accessibility has failed as a way to make computers usable for disabled users." Thus begins a newsletter by Jakob Nielsen. And had it not been written by someone a great many people take seriously in the UX industry I likely would just have dismissed it. But seeing how harmful I consider the post to potentially be, I would like to nip this in the bud. My reflection is that the published post is misleading, self-contradictory and underhanded. I'll walk you through the whole of it and provide my commentary and reasoning.

CSS has an infinity constant. When I first learned about this, my brain lit up with all kinds of absurd possibilities. Let’s discuss! There might even be some practical use cases.

I’ve been extremely critical of shadow DOM in the past, and declarative shadow DOM remedies a large part of that. I think it’s finally time to start thinking about incorporating shadow DOM into our everyday workflows. This post will cover the what, the why, and the how of using shadow DOM today.

With classes, we can send CSS static values but with custom properties we can send dynamic ones, which is a major shift in the way we can style state. This is something that has been true for some time—and is extremely well supported—but sometimes it takes solving a small real-world problem to make you appreciate the value of it.