On the Uniting Power of a Commitment to HTML Conformance
HTML is the language of the Web. No matter what other languages are being used, in the end it all boils down to content and functionality being represented by HTML.
Unfortunately, our field, the field of web and frontend development, doesn’t commit to any quality standard—that is, expectation—for HTML.
It’s not that no such standard existed—arguably, the baseline is conformance with the HTML specification—, it’s that this standard is being ignored.
This isn’t hyperbole: When you validate—check on conformance—the most popular websites, none (0) uses valid and conformant HTML.
It’s similar for websites for frontend documentation, tools, and starter projects.
Even when you turn to the websites of web developers, it’s the exception, and not the rule, that there would be no conformance issues.
The reason for this misery is not the point of this article—apart from myself, several of our peers have long hypothesized about this in other fora.
The point is also not that we miss what this lack of a quality standard means for the value of our field—that instead of increasing it, we deflate it.
The point is that we miss an exceptional opportunity to unite behind it.
Imagine, just for a moment, if we as web and frontend developers would all produce conformant websites, and all ran conformant websites.
“This document was successfully checked as HTML,” as the W3C validator says.
This, for once, could be uniting; it could get us from indifferent or apologetic ignorance to mutual respect and healthy pride of being a member of our field.
It could allow us to tackle more serious challenges—like pushing harder on accessibility—with collective vigor.
That unity, that feeling, is something our field has always lacked. Can we finally change this? Can we finally convince our peers? (Are you on board?)
Together, we could lead by example, together we could establish our field’s first quality standard—an objective and proven, a light but robust foundation that we, as professional frontend developers, can build on.
I’m Jens, and I’m an engineering lead and author. I’ve worked as a technical lead for companies like Google, I’m close to W3C and WHATWG, and I write and review books for O’Reilly and Frontend Dogma. I love trying things, not only in web development, but also in other areas like philosophy. Here on meiert.com I share some of my views and experiences.
If you have a question or suggestion about what I write, please leave a comment (if available) or a message. Thank you!
Maybe of interest to you, too:
- Next: Existence and Experience
- Previous: What Happened to Separation of Concerns in Frontend Development
- More under Web Development, or from 2023
- Most popular posts
Looking for a way to comment? Comments have been disabled, unfortunately.
Get a good look at web development? Try WebGlossary.info—and The Web Development Glossary 3K (2023). With explanations and definitions for thousands of terms of web development, web design, and related fields, building on Wikipedia as well as MDN Web Docs. Available at Apple Books, Kobo, Google Play Books, and Leanpub.