Introduction: Standards? Who Really Cares Anymore?
Are Web Developers Neglecting Standards?
Are web developers disregarding standards? A recent analysis of the biggest websites indicates they might be. ValidateHTML, a project initiated by independent French developer Théo Ducreux, assessed the content of the 5,000 most popular web domains, based on the Tranco research initiative.
The Usual Contenders and Some Strange Entries
These include the usual contenders (Google, YouTube, Akamai) along with those that don’t have public interfaces (Google’s “gstatic,” EZVIZ’s “Ezviz7”). Ducreux discovered that over half – 2,656 sites – provided a homepage that humans could read. Many others, including Google and EZVIZ’s, were merely traffic redirect pages, directing back to a company’s products.
HTML Issues Across the Board
Regardless of being headless or not, about 90 percent of these sites failed to deliver proper HTML, as defined by the World Wide Web Consortium (W3C) and the WHATWG (Web Hypertext Application Technology Working Group). These standards are crucial for ensuring that various browsers and reading tools can display requested pages similarly.
The Figures Don’t Deceive
Ducreux recorded a total of 100,305 HTML infractions (including the latest HTML5 specifications) across all these sites, along with an extra 18,863 CSS mistakes. This means that 87.2 percent of sites breach web specifications at least once. Only 12.8 percent have completely valid HTML. Furthermore, just 2.6 percent of all sites are entirely error-free, returning no errors or best-practice alerts.
Accessibility: The Overlooked Metric
More concerning, over a third of sites did not pass accessibility evaluations, which is considered more of a legal risk (and thus a compliance matter) than a source of shame for their owners, especially with the upcoming 2025 European Accessibility Act. (In the U.S., beware the accessibility-unmindful e-commerce site that provokes the National Federation of the Blind.)
Alt Text and ARIA Label Issues
From an accessibility standpoint, 20.4 percent of sites lack alt text on images, which often carry crucial information. Even worse, 41.6 percent of pages lack ARIA labels that designate page regions, potentially causing screen readers to struggle with conveying the page structure.
Théo Ducreux’s DIY Coding Journey
The Custom Tech Behind the Findings
“Screen readers have nowhere near the error tolerance that Chrome does, so markup that seems perfectly fine to you may be flawed for someone using assistive technology,” Ducreux shared with GadgetLad. For his project, he utilized a custom-built web crawler and a series of open-source parsers (HTML-validate, CSS Validator, Lightning CSS, fast-xml-parser). “The website, the scoring system, and the crawling logic are all my own creations,” Ducreux detailed via email. Ducreux serves as the principal maintainer for the project and site. “No team, no funding, no organization.”
Does It Truly Matter?
The Web as a Collaborative Endeavor
Does noncompliance with standards truly hold significance? It’s a valid inquiry. “The web is primarily a social construct rather than a technical one,” web pioneer Tim Berners-Lee stated back in 1999. If everyone begins creating their own standards, it complicates connections and communication.
Browsers and Their Lax Tolerance
The currently popular Dead Internet Theory – suggesting that AI machines and not humans now constitute the majority of internet traffic – won’t absolve developers. As Shopify engineers discovered, even superintelligence leans towards well-structured markup. Browsers also bear part of the responsibility. Unless they have a penchant for the ephemeral but brutally strict XHTML, contemporary browsers will simply disregard any code they cannot comprehend.
Frameworks Engaging in Mischief
“Browsers are so proficient at error recovery that there’s nothing compelling anyone to correct” their code, Ducreux noted on the site, “which is precisely why it builds up.” Leeway breeds negligence. Front-end frameworks contribute their own brand of chaos. The single most frequent issue identified (in over 59 percent of all sites) is misplaced elements, also known as incorrect tag nesting.
HTML: A Threat to Existence or Just an Irritant?
Ducreux himself doesn’t view faulty HTML as an existential threat to the web, except for hampering accessibility, which can leave individuals guessing about online content that they may genuinely need to understand. “Honestly, most invalid HTML doesn’t disrupt anything visible; browsers are designed to interpret your intentions and silently correct issues,” he wrote via email.
Beyond Browsers
However, the web is not solely reliant on browsers. “AI agents reading pages, voice assistants, translation tools, screen readers – none of them possess Chrome’s 20 years of guessing your intent,” he explained. “Adhering to specifications ensures a page conveys the same meaning to all of them, not just to whoever is rendering it in Chrome that day.”
Conclusion
Keep It Tight or Face Consequences!
Bear in mind, folks, careless HTML might not disrupt browsers, but accessibility is a game-changer. In the tech sphere, slacking off isn’t an option. So, refine that code, or endure the consequences from the pixel enforcers!
