Designing with web standards: The playbook for this AI moment

Every team building with artificial intelligence right now believes it is working on a blank frontier. New interface, new rules, no map.

That belief is wrong, and it is expensive.

The cost is not hypothetical, and it shows up as rework, as users who never trust the tool, and products that age quickly. It feels a lot like 1997, when the web was the wild west almost literally.

A handful of browsers each went their own way. Netscape Navigator, Internet Explorer, Opera, and the fading remains of Mosaic rendered the same page differently, each with its own proprietary tags, thinking they had invented sliced bread:

• Netscape, specifically Lou Montulli, gave you a blink tag, but he claims it was implemented by someone else.
• Microsoft answered with a scrolling marquee. No one wanted to take credit.

Both quite honestly sucked, but it was early times. A site built for one broke in the next, so designers rebuilt the same thing three times and called it a living.

Then a small group decided the chaos was a choice and not a fact of nature, and they made the case for standards. L. Jeffrey Zeldman was the lead pirate.

Zeldman did not invent the specifications, he did something harder: He convinced an entire industry that shared conventions were worth fighting for, and he won. Zeldman changed the world with a stance, not a specification and we should thank him for it.

We are living through that moment again, this time for the interfaces we wrap around models, the skills we scaffold on top of them and representations they mean.

The browsers have new names: ChatGPT, Claude, Gemini, and Copilot each handle the same task their own way, with their own conventions for parsing content, showing reasoning, citing a source, and asking permission before they act.

There are no shared standards to make them consistent, so the patterns are unsettled, the vendors are playing jazz, and the window to shape the conventions is open.

What Happened Before: Zeldman and the Fight for Web Standards

Most designers now arrive in the field with no working knowledge of how its standards were won— who fought for them, against what, and why it mattered. A profession that forgets how it climbed out of its last mess is well positioned to climb back in.

Jeffrey Zeldman is, in the phrase Business Week gave him, the King of Web Standards. In 1998 he founded A List Apart, the magazine for people who make websites, which became the place where the craft argued with itself and got better. That same year he co-founded the Web Standards Project, a grassroots coalition of designers and developers with an unglamorous goal: get the browser makers to support the same technologies the same way.

This was grassroots in the literal sense. The pressure came up from the people closest to the markup — the ones paying the daily tax of the chaos — rather than down from above.

The Browser Wars

Browser makers treated the web as territory to capture, not a commons to tend. Microsoft and Netscape shipped incompatible features by design, because lock-in was the strategy. Zeldman and his collaborators spent years making the case, in public and in private, that this served no one over the long run.

The Argument That Outlasted the Tools

His 2003 book, Designing with Web Standards, was the argument in its most durable form. Zeldman’s real achievement was never a specification, it was a shared belief that the web should work the same way for everyone, held widely enough that building any other way started to feel embarrassing.

Standards won because enough people decided they should.

Why It Matters: What the Standards Movement Won

A semantic separation as a standard

The core move was to pull structure, presentation, and behavior into distinct layers so each could change without breaking the others. That one idea outlived every specific technology it was built on. AI is that problem at a larger scale, and the answer is the same shape: a shared, documented, governed system instead of a fresh pile of one-offs per product.

A business case before the moral one

Zeldman did not lead with accessibility as a virtue, though he believed in it. He led with cost and reach, which was exactly the right lever: standards-based sites cost less to build, load faster, and reach more people. If you want a convention to spread, make it cheap, not just the righteous.

A coalition, not a command

No one had the authority to mandate standards. The standards did not come down from a committee; they came up from practitioners who agreed with each other, in public, until agreement became the default.

Why We Need It Now: The AI Interface Moment Is 1999 Again

Jakob Nielsen has called this the first new user interface paradigm in sixty years — a shift from telling the computer how to do a thing to telling it what you want and letting it decide how. That inconsistency carries a cost people are only starting to name. When every model formats its reasoning, its sources, and its confidence differently, you cannot line two answers up side by side.

We are pouring the same proprietary concrete, only faster and with more money behind it.

What It Should Look Like: Building Shared Standards for AI Interfaces

• Name the patterns before the vendors lock them in. Agree on what “show your work,” “cite your source,” and “I am not sure” should look and behave like, as reusable components rather than one-off features.
• Make traceability and confidence first-class parts of the interface. The most dangerous thing an AI interface can do is present a guess with the same visual authority as a fact.
• Build the coalition, not the mandate. Publish your patterns, argue for them, and adopt other people’s good conventions instead of reinventing them.

The New Markup Is Markdown

Agents increasingly take their instructions from plain text files that sit beside the work — AGENTS.md for how an agent should behave, SKILL.md for what a capability can do, README.md for the context. This is the new semantic layer. It is markup again, written in Markdown and read by a model instead of a browser.

The W3C Already Built the Machinery

The W3C has run an open, consensus-based standards process since 1994. The division of labor back then is worth remembering: the W3C wrote the standards, and the Web Standards Project made adoption non-optional. That machinery did not disappear; they have already launched a Web and AI Interest Group to work through how AI technologies intersect with the web.

The standards moment is not a prediction. It is a choice, and it is being made right now, mostly by default. We are the practitioners now. The models are astonishing and the interfaces around them are a mess, which is exactly the condition Zeldman walked into and refused to accept.