This post is a rant attempting to express what seems to be a growing issue: lack of deep thought behind writing HTML for webpages—that will go to production! 🤓 Yes, more time is spent writing that animation, that slider, that app like experience than prioritizing what would probably ensure that customers come to webpages and have a better experience: semantic valid html.
Developers bulldoze right past truly thinking about HTML. It makes sense! Complex tasks where benefits of thoughtful HTML are just not considered. Not only that, project goals are iterative—they are grown upon and updated in steps. Questions like, is the HTML valid? or is the HTML semantic? are never asked. This small issue then grows on a webpage as new features are added and other websites follow a similar pattern. The world and developers think it’s fine because browsers have improved and the webpage looks fine—but is it?
Questions like, is the HTML valid? or is the HTML semantic? are never asked.
Developers, product managers, maybe the whole world at this point assumes it is easy to write Semantic html. We should not! Semantic HTML makes webpage content more legible to browsers, search engines, other developers, and is much easier to maintain. Yet, when looking at source code on many webpages, it is easy to find html that could be semantically improved.
Beyond Semantic HTML, valid HTML is an issue! With browser advancements, checking whether html webpages validate just doesn’t happen.
Validation may not be an issue for Google and Facebook because there usership maybe be so large. However, most websites are not Google or Facebook. This is where the point of valid html is still be a very important thing to consider! 💭
Companies looking to grow their audience through webpages should always look to provide rich experiences that can be shared across the most possible platforms in the easiest way. Valid and semantic html would definitely make that easier and with less long run effort.
Years ago when writing html for webpages, everything that was done had to pass the w3c test. HTML validation tests were even looked at as a tool to find unclosed element tags and fix layout issues. Sure, there where a lot of
divs but we could make a webpage render in Internet Explorer 6 as expected!
Sure, there where a lot of
divsbut we could make a webpage render in Internet Explorer 6 as expected!
As browsers became better, HTML5 elements became more supported, and jQuery allowing easy Dom manipulation HTML testing and review seemed to become more and more of an after thought. Then, the iPhone came and Apps took a front seat. Everyone wanted an App and webpages to look like Apps so whether a webpage’s HTML was valid or not didn’t matter.
Now, years later, we know people don’t go to many webpages and they don’t use many apps so webpages have to be consumable for websites people do go, usable for when people do get them, and fast for when they are viewed.
High quality html is:
- Consumable: when webpages are consumed by third party services like Medium and Facebook instant articles, high quality HTML is probably much more consumable.
- Usable: thoughtful HTML is much more usable for people with special needs and people in general.
- Fast: browsers can probably render thoughtful HTML better.
Here are a few tools that can be used to write better html:
With tools like AMP, it may not ever be necessary but even then the matter of creating common ways of writing html is important—even more so with HTML5 and it’s new elements and attributes that come along with it.