A validator ran HTML and CSS checks against the Tranco top 5,000 domains, successfully reaching 2,655 home pages. 90.5% of those violate the HTML spec, with the most common issue being invalid element nesting (59.5% of sites), typically caused by framework-generated markup. Accessibility failures such as skipped heading levels, missing form labels, and empty link text each affect over a third of sites. CSS errors are less pervasive (65.1% of sites) but usually consist of a single broken declaration, most often an invalid property value, that browsers silently ignore. The study excludes checkout flows, dashboards, and CMS pages, covering only home pages of high-traffic sites measured in August 2026.
Questions this post answers
What percentage of top websites have valid HTML?
Only about 2.6% of tested home pages come back completely clean against the HTML spec. Among the 2,655 reachable domains from the Tranco top 5,000 that were checked, 90.5% had at least one HTML spec violation, totaling 100,399 violations across 220 distinct error message families. See how daily.dev surfaces frontend quality and accessibility discussions for developers auditing sites.
What is the most common HTML validation error on real websites?
The most frequent HTML spec violation is invalid element nesting, such as a style element placed directly under a div, appearing on 59.5% of sites tested. This typically isn't a hand-written typo but a byproduct of components composed by frameworks that don't know which element they're being dropped into, making it a build-time issue rather than an editor mistake. Developers debugging framework-generated markup issues can follow related discussions on daily.dev.
How common are web accessibility errors like missing form labels or empty link text?
Accessibility failures are near-universal among popular websites: missing form labels affect 43% of sites, skipped heading levels 46.4%, empty link text 37.7%, and empty button text 22.2%. These findings matter beyond style since the European Accessibility Act has applied since June 2025, turning these into a compliance issue rather than a preference. Track accessibility compliance requirements and fixes as they evolve by following webdev topics on daily.dev.
305.9K Impressions6 Comments