My post on two-state dark mode toggles sparked a lot of discussion about the optimal dark mode toggle design. But should you have a (persistent) dark mode toggle at all? I have since been convinced that for most websites, the answer is no.
I think the better alternative would be for browsers to have some kind of per-site override instead of relying on every single site building the same system and putting the option in a different place.
If a setting is universally supported by all sites (which dark mode should be, along with the other common accessibility flags), it shouldn’t be something that the site needs to control.
It probably wasn’t clear in my post but I’d be happy with the toggle being in the browser (not something I’ve historically thought about but a great idea), it was more about the existence of a toggle.
I do agree with @jaredwhite@humansare.social that having the toggle in the header is a waste of space.
Same with horizontal tabs.
I think the better alternative would be for browsers to have some kind of per-site override instead of relying on every single site building the same system and putting the option in a different place.
If a setting is universally supported by all sites (which dark mode should be, along with the other common accessibility flags), it shouldn’t be something that the site needs to control.
It probably wasn’t clear in my post but I’d be happy with the toggle being in the browser (not something I’ve historically thought about but a great idea), it was more about the existence of a toggle.
I do agree with @jaredwhite@humansare.social that having the toggle in the header is a waste of space. Same with horizontal tabs.