Study finds only 2.6% of top websites have fully valid HTML
A validator audit of the Tranco top 5,000 domains finds nearly all violate the HTML spec, sparking debate over whether that still matters.
What to know
- The audit found 90.5% of the top 5,000 most-visited domains have at least one HTML spec violation, with only 2.6% (69 sites) fully clean of errors and warnings.
- The most common issue, present on 59.5% of sites, is a structural nesting violation attributed to framework-generated markup rather than manual coding mistakes.
- Critics on Hacker News dispute the framing, arguing the 2.6% 'clean' figure conflates best-practice warnings with actual spec violations and that HTML5's error-tolerant parsing has made strict validity largely moot.
- Accessibility-related failures (heading structure, unlabelled inputs, links without text) appear on over a third of sites, which commenters and the report link to compliance exposure under the EU's Accessibility Act.
The dispute Whether invalid HTML represents a real quality/compliance problem or is a harmless artifact of an error-tolerant, framework-driven web that no longer matters in practice. · positions read across 13 posts and comments
HTML validity stopped being practically important once HTML5 standardized how browsers parse invalid markup.
-
“This is no longer anywhere near as important as it used to be because HTML5 defines a method for turning more-or-less any sequence of bytes into the same DOM tree”
jerf · Hacker News
The study's headline and methodology are misleading or flawed.
-
“The 2.6% figure only includes websites that also follow some arbitrary set of "best practices" in addition to being valid HTML, some of which actually contradict best practices from the past.”
account42 · Hacker News
Full HTML validity is now a niche point of pride rather than a practical necessity.
-
“As someone who valued that "Validated by w3c" button on my website back in the day, if a website today has FULLY valid HTML, I gaurantee you the admin is a massive nerd.”
INTPenis · Hacker News
“Valid HTML is the exception, not the rule. Nine sites in ten among the most visited on the web violate the standard on their home page, and 2.6% come back completely clean.”
validatehtml.com, Report author · validatehtml.com · Aug 10
validatehtml.com Publisher of the HTML validity researchtheo_dcrx Hacker News submitter
The record 2 articles and posts · last 30 days
What people are saying 12 voices from 1 site · best of 13 · verbatim
- Does the 2.6% 'fully clean' figure reflect true spec compliance or an inflated bar that mixes in subjective best practices?
- How much of the accessibility-related failure rate translates into actual legal exposure under regulations like the EU Accessibility Act?
- Aug 13
-
Any website that writes the literal T&Cs would fail on `Unrecognized character reference "&Cs"` so it's not surprising only 2.7% are 'clean'
-
It never mattered. It only mattered that your site worked in the big browsers. Internet Explorer then, Chrome and iOS Safari now.Developers would write their standards-compliant code, boast about it on Slashdot, then put in the hacks and weirdnesses to make it work on IE6. They could have skipped the standards step.I don't say this is a good…
- Aug 12
-
I take this to mean that only 2.6% of these websites are trivial enough to be written with a tiny subset of HTML.
-
As an aside, what is up with the design of clearly vibe-coded websites? You can tell it's AI from intuition, but is there a list of "tells"? Like black background, gradient text, font? Would love to learn more and how to combat
-
> "Valid HTML" used to be a big dealTo a point that there was an actual badge for it.
-
To a first approximation, this doesn't matter anymore. "Valid HTML" used to be a big deal because when you left the HTML spec you were inviting the various browsers to interpret your non-standard HTML in differing ways, sometimes quite catastrophically so for the styling or how the Javascript would interact with the page.This is no longer anywhere…
-
The claim in the title does not match the linked website. The 2.6% figure only includes websites that also follow some arbitrary set of "best practices" in addition to being valid HTML, some of which actually contradict best practices from the past.
-
> An unclosed tag occurs when an opening HTML tag like <div>, <p>, or <span> is missing its corresponding closing tag.Since when does <p> requires a closing tag? Note that TFA lists this among "spec violations" and not merely "best practices".
-
As someone who valued that "Validated by w3c" button on my website back in the day, if a website today has FULLY valid HTML, I gaurantee you the admin is a massive nerd.
-
50% of my errors are “<font> is deprecated”. If browsers stop supporting that I’m guessing huge swathes of the web will be affected, so I’m guessing it will never happen.
-
This is exactly why HTML is so ubiquitous, because it is so tolerant of mistakes in formatting, syntax, and just about anything else.Most browsers will even read and process most of the things listed on this page because even if the spec doesnt say so, it just makes sense to anyway.
-
I would def argue this is a feature of the net ( that people from all walks of browsers can see mostly the same thing ) and not a bug.