W3C Validation is a Waste of Time

There's a reason why Google, Amazon, Ebay, Apple and many more sites don't validate. It is not realistically feasible. Allow me to explain; on the face of it you might think that if a web developer doesn't ensure their HTML is valid they must be lazy, right? Wrong!

If you build a website and complied with the triple-A standards, how would you expect it to look in all the different browsers? Exactly the same? You followed all the rules, dotted the i's and crossed the t's right? Wrong! Different web browsers have varying degrees of compatibility with the W3C specifications. IE6 is the worst offender that is still commonly used today. So even if you design your HTML to W3C standards it does not mean it will render correctly in IE6. So what do you do, well you can take those things out and limit your creativity or you could look at various tips and tricks, hacks and what-nots to get IE6 up to speed. But these are the sorts of things that can prevent your site from validating. But who really cares about validation right, surely the most important thing is the end user. And the end user is looking at your website using IE, Firefox, Safari and Chrome - they are not using the W3 validation service.

So does this mean I hate the W3C. Not at all, in fact as a web developer I really appreciate what they do. They make the rules for the browser vendors to follow. They create common ground so that surfers can get a consistent experience regardless of which web browser they are using. The more consistent web browsers are - the easier it makes my job. The browser vendors build browsers according to the spec. Then I build websites according to what works in the browsers.

07/10/2010 permalink | Posted in web development | 0 Comments »

Bookmark and Share

About me

Adam Jimenez is a freelance web developer who has been professionally developing websites since 2000.

Find me