Most popular websites break the HTML standard on their home pages. A fresh analysis of the Tranco top 5,000 domains found that 90.5 percent of readable home pages carried at least one spec violation. Only 2.6 percent returned completely clean.
Validate HTML ran the same validators offered on its site across 2,655 reachable pages in August 2026. The result: 100,399 HTML violations and 17,599 CSS errors across 220 distinct message families. Validate HTML published the full ranking on August 11.
Median sites showed 12 HTML errors. The mean reached 37.8. One outlier hit 2,209. A small tail of sites drives most of the volume. Distinct rules broken matter more than raw counts for audits.
Nesting problems led the list. The top message, an element not permitted as content under another, appeared on 59.5 percent of sites. Frameworks compose components without checking context. That creates the issue at build time.
Accessibility gaps showed up everywhere. Missing form labels, skipped heading levels, and empty link text each affected more than a third of pages. The European Accessibility Act has applied since June 2025. These count as compliance risks now.
CSS errors followed a different pattern. 65.1 percent of sites had at least one. Yet the median stayed at one. Invalid property values dominated. Browsers simply drop the bad line and continue.
WebAIM’s 2026 Million report painted a similar picture on accessibility. 95.9 percent of one million home pages carried detectable WCAG failures. Average errors per page rose to 56.1, up 10 percent from 2025. WebAIM released those findings in March.
Structural issues outranked simple typos. Duplicate IDs, missing alt attributes on images, and stray end tags rounded out common failures. Many trace back to templates or automated generation rather than hand coding.
The study covered home pages only. Other sections of sites likely fare worse. Popular domains reflect mature teams and stacks. Smaller sites may differ.
Validators apply conservative rules. Different tools produce different counts. This snapshot reflects one engine’s judgment on August 11, 2026. Sites evolve quickly.
Frameworks and build tools keep introducing the same nesting violations. Browsers forgive the rest. That forgiveness lets problems persist in production.
Fix guides exist for many of the top issues. Teams that audit per rule rather than per occurrence gain clearer priorities. The data shows where effort yields the fastest compliance gains.