---
title: "Web Standards Crisis: Nearly 90% of Popular Sites Violate HTML and CSS Rules"
description: "The ValidateHTML study showed that 87.2% of popular sites violate web standards. This creates serious accessibility issues for people with disabilities and jeopardizes the correct rendering of content."
date: 2026-08-19T00:17:50.000Z
lang: en
url: https://xab.info/en/posts/web-standards-crisis-90-of-sites-violate-html-and-css-rules
tags: [web-development, html5, accessibility, validatehtml, seo, coding-standards]
publisher: "XAB.info"
---

# Web Standards Crisis: Nearly 90% of Popular Sites Violate HTML and CSS Rules

![Code editor screen showing HTML markup with typical web standards violations — excessive div containers and misused Bootstrap classes](https://xab.info/media/2026/08/19/krizis-veb-standartov-90-sajtov-narushajut-pravila-html-i-css/krizis-veb-standartov-90-sajtov-narushajut-pravila-html-i-css-1.webp)

## 🎯 Key Points

- Only 2.6% of 5,000 popular sites have completely clean code without errors.
- More than a third of sites are incorrectly processed by screen reader software.
- On 41.6% of pages, necessary ARIA accessibility labels are missing.
- Modern browsers mask code errors, which reduces developers' motivation to fix them.

In August 2026, independent French developer Théo Ducreux presented the results of a large-scale web code quality audit in the ValidateHTML project. The study covered the 5,000 most popular domains in the world, and the results were shocking for the industry: nearly nine out of ten sites contain errors that violate basic World Wide Web standards. This points to a systemic crisis in development quality, where the speed of product release is often prioritized over technical correctness and accessibility.

### The Scale of the Problem: 100,000 Violations

During the analysis of the sample of 5,000 domains, it was found that only 2,656 of them are full-fledged websites intended for humans. The remaining addresses were used as technical domains (for example, Google's "gstatic" infrastructure). Despite this, even among "human" sites, the situation is critical. In total, more than 100,305 violations of HTML code correctness were found on all checked resources, including HTML5 specifications, as well as nearly 19,000 CSS errors.

The statistics of perfection look even more alarming: only 12.8% of sites were deemed to have correct code. Completely "clean" resources that did not produce a single error or warning were only 2.6%. This means that the vast majority of internet users interact daily with technically incorrect pages, which can lead to unpredictable content rendering on different devices.

### Accessibility Crisis for People with Disabilities

One of the most serious problems identified during the check was the inaccessibility of web resources for people with visual impairments. More than a third of sites failed the accessibility check, meaning they are incorrectly processed by screen reader software. W3C and WHATWG standards were created specifically to ensure identical interpretation of content by all browsers and assistive technologies, but in practice, these norms are ignored.

Key accessibility metrics are also at critically low levels. Alternative text (alt text) for images, which often contains vital information for blind users, is missing on 20.4% of sites. Moreover, on 41.6% of pages, ARIA labels are completely absent from the code — special attributes that identify page areas and help navigation for screen readers.

### "Guilty" Browsers and Frameworks

Experts identify two main culprits in the current situation: developers and the browsers themselves. Invalid code is often a byproduct of working with modern frameworks. The most common error is incorrect tag nesting, which is technically impermissible but often found in generated code.

However, the main reason is the "unpretentiousness" of modern browsers. They are so smart that they can ignore code errors and automatically restore the desired page layout. This creates an illusion of safety for developers: if the site looks normal in Chrome or Safari, everything is fine. Unfortunately, screen reader software does not possess such "resilience" and requires strict adherence to standards to correctly voice content to the user.

## 🔍 Fact-Check Verification

- [Almost 9 out of 10 sites caught violating web standards window-new](https://3dnews.ru/1147015/pochti-9-iz-10-saytov-ulichili-v-nesoblyudenii-vebstandartov) - Основной источник данных о проекте ValidateHTML и статистике нарушений.

## ❓ FAQ

### Q: What is ValidateHTML?
**A:** It is a project by independent French developer Théo Ducreux that conducts audits of the validity of code on popular websites.

### Q: Why are errors in HTML code dangerous?
**A:** Errors violate W3C standards, leading to incorrect page rendering and making them inaccessible to people using screen reader software.

### Q: How many sites in the study had perfect code?
**A:** Only 2.6% of sites from the sample of 5,000 domains turned out to be completely clean without errors or warnings.