Don't. Ever. Publish. Stuff. That. ONLY. Supports. Dark. Mode.

I mean, I know a LOT of people love dark mode, and given the benefits that darkening interfaces provides... I get it.

But there are some people (like me) who may be visually impaired. Astigmatism, for example, can make reading text that is white on dark a real PITA. An effect known as "halation" occurs, where each letter behaves as if it were a flashlight, gaining its own halo of light and making all text read more blurry than normal.

No matter how good your glasses are, astigmatism still causes you to see a little blurry—it's something you get used to. But this damn effect makes all the text read as if you don't have your glasses on, or even worse, leading to much more tired eyes or even pain.

For everyone's sake, if you really care about accessibility, respect user preferences. If you want a dark interface by default, offer a light version if the user specifies it (in web design, this would be
prefers-color-scheme: light). The same goes for light interfaces.
@naipotato thanks for writing this. As someone who has a strong preference for dark mode (light mode really strains my eyes even on lowest brightness, but I can manage), I've often wondered if there was an accessibility aspect to using a light theme in preference to dark. I'm curious whether this also applies to elements where it might be generally "light mode" themed but have an isolated widget like a mid-blue button with white text (as an example), something I see often in UI toolkits - are those troublesome too?
@ds They usually don't cause much problem, because they are small and isolated. The problem arises when more than 50% of the screen is dark.