Designing for the unstyled web
How to ship interfaces that survive a missing stylesheet — and why you should.
Most of the web we ship looks fine — until the stylesheet doesn't load. A flaky CDN, an aggressive corporate proxy, a feature-policy header that strips your fonts. Suddenly your beautiful site is a wall of unstyled HTML, and the question becomes: is it still usable?
The technique I keep coming back to is 'semantic-first, decorative-last': write the HTML so it reads top to bottom like a well-structured document, and treat CSS as polish. The default user-agent stylesheet handles 70% of the work for free.
Once you do this, the unstyled fallback isn't embarrassing — it's usable. Forms still submit. Navigation still works. And the moment your CSS lands, the whole thing snaps into place with no jarring layout shift.