Web Standards
Standard Compliance Has Two Meanings
"Standards-compliant" means one thing for authors and another for browsers; conflating them starts pointless fights.
"Standards-compliant" means one thing for authors and another for browsers; conflating them starts pointless fights.
Few phrases start more circular arguments than "standards-compliant." One developer means their markup follows the rules; another means the browser renders correctly; a third means the page works everywhere. They're all using the same words to describe different things, and until everyone notices, the conversation goes nowhere. The specifications themselves are clearer than we are: compliance has two distinct audiences.
Modern web specifications are written to bind two very different kinds of software, and they define requirements for each separately.
This is the set of rules that apply to you — the person or tool producing the document. It says what markup is allowed: which elements exist, where they may appear, what attributes they take, what values are legal. When a validator flags your page, it's checking authoring conformance. "Don't put a <div> inside a <span>" is an authoring rule.
This is the set of rules that apply to the browser — how it must parse, render, and behave given any input, including input that violates authoring rules. Crucially, the spec defines what a UA must do even with invalid documents. "When you encounter an unexpected end tag, do this" is a UA rule.
Authors are told what they may write. User agents are told what they must do with anything, valid or not.
Splitting the two is not bureaucratic hairsplitting; it's the mechanism that makes the web robust. Authoring rules keep documents clean and interoperable. UA rules guarantee that even a broken document produces the same result in every conforming browser. So a piece of tag soup can be simultaneously:
Both statements are true at once. That's not a contradiction; it's the whole point. The author made a mistake, and the platform ensures the mistake at least fails uniformly.
Now the arguments make sense. When someone says "my invalid page is fine, it works in every browser," they're claiming UA-side consistency — and they're often right. When someone else says "your page isn't standards-compliant," they're pointing at authoring conformance — and they're also right. Neither is wrong; they're grading different exams.
The useful move is to name which meaning you're using. "This document doesn't conform as authored, though browsers handle it consistently" is a sentence that ends the fight instead of fueling it. Aim for authoring conformance because it's the layer you control and the one that protects your document's meaning; rely on UA conformance because it's the layer that saves you when you slip. Two meanings, two audiences, one platform that needs both.