Michaël Vanderheyden

@th3s4mur41.me

Lead UX Engineer & Accessibility Specialist @ cycos, an Atos Business #CPWA #WebDev #A11y #CSS Martial arts lover | Shotokan Karate black belt | BJJ practitioner | Bikejöring https://th3s4mur41.me

QQ about Dark Mode Toggles on websites How many options do you show to users? - Three values: System, Light, or Dark - Two values: Light, Dark (with one of them mapping to “System” behind the scenes). Why the one or the other? (I have an opinion about it, but I’m looking for external input)

My colleague Julia Undeutsch built "Div & Die": a game where players must guide a blind pedestrian across a street. Because the map uses only generic <div> tags, screen readers can't detect the tactile guidelines or white cane cues. A perfect look at why semantic code is vital!

Screenshot of 'Div & Die', a 2D game testing semantic HTML. The left side shows a top-down view of a pedestrian with a white cane attempting to cross a busy street via tactile paving. The right side shows the game's code panel filled entirely with non-semantic nested div tags instead of structural HTML landmarks. Text instructions warn that without semantic elements, a screen reader cannot intercept the environmental cues or landmarks needed to cross safely.

Adding proper arrow-key navigation to custom UI used to require tedious event handling. I’ve been experimenting with the new focusgroup API, and the simplicity is incredible. You get native, accessible UX out of the box while deleting custom JS. My first deep dive: th3s4mur41.me/blog/focusgr...

Focusgroup: The Future of Keyboard Navigation

Chrome and Edge 150 shipped native focusgroup support — an HTML attribute that brings arrow-key navigation to the browser, with automatic ARIA roles and a polyfill available today.

th3s4mur41.me

Just published a blog post about the new CSS Anchor Positioning API! ⚓ I’ve been learning about it over the past few weeks, and it’s friggin’ great, but it also took me a minute to really get the hang of it. My goal in this post is to share the most useful bits, so you can start using it today. 🔥

Getting Started with Anchor Positioning • Josh W. Comeau

For decades, one of the most notoriously-challenging problems on the web has been sticking one element to another element, for things like tooltips and nested menus. The CSSWG has decided to provide a...

joshwcomeau.com

Design systems have always intrigued me, but they are something that I don't have any experience with, so, I've teamed up with someone who does have that experience!, @michaelwarren.dev! It's still early days, but if you want updates as we work on it, sign up here: thecascade.dev/courses/desi...

Thoughtful Design Systems - a course by Kevin Powell and Michael Warren

Founded by Kevin Powell, with curated learning paths, courses, and clear explanations that will have you writing CSS with confidence.

thecascade.dev

Did you attend #CSSDay and saw my talk (or heard about it), and you really want CSS Grid Lanes to be supported across browsers? ➡️ Give this issue a thumbs-up *and* add a comment explaining your use case. This can help a lot move things forward 💟 github.com/web-platform...

Masonry · Issue #308 · web-platform-dx/developer-signals

This GitHub issue is for collecting web developer signals for Masonry. The display: grid-lanes or display: inline-grid-lanes CSS declaration creates a layout where items are tightly packed, like br...

github.com

In a world of AI-generated design systems, orchestrating the web still requires people who care. Knowing how to use smart layers, custom scrollbars, view transitions, and have accessibility on top of mind is what builds a joyful UX. 🧑‍💻 Systems should be scalable. utilitybend.com/blog/the-dea...

The death of Web UI? Bollocks! Geeking out on a better web and trying to make a difference. | utilitybend

CSS Day 2026 reminded me that Web UI isn't dead — just dormant. Why tinkering with CSS still matters in a world of AI-generated design systems.

utilitybend.com

Is your "Back to Top" link breaking your UX? href="#" might be valid HTML, but it creates a major accessibility focus desync—scrolling the screen for sighted users while trapping keyboard focus at the bottom. Read why your linter is right to hate it: th3s4mur41.me/blog/href-ha...

href="#" and the Focus Trap

An empty href="#" is valid HTML — but it scrolls the page without moving keyboard focus, silently breaking WCAG 2.4.3. Here's why, and the one-line fix.

th3s4mur41.me

YES, Dark Mode Toggles _should_ be a browser feature. I wrote about this before: brm.us/dark-mode-ov... Find the link to the Chrome Bug in the post, and hit the star next to it to "upvote" the bug. (I even have a prototype extension to provide this for you: brm.us/chrome-dark-...) #cssday

Dark Mode Toggles Should be a Browser Feature

When implementing Dark Mode and ways to toggle it, developers currently need to duplicate code and roll their own toggle implementation. What if, instead, browsers would take care of all that?

brm.us