Why web standards DON’T suck


While this story is far from new, nearly three years old as I write, in fact, if this can’t convince you – or your clients, perhaps more importantly – that web (re)development using recognised and proven web standards is a worthwhile, then there’s no way you’ll ever be convinced. Even today, I find significant resistance among my clients for a semantic markup and CSS approach to their redevelopments. More often than not, that resistance is driven by a perception (albeit a false one) that semantic markup and CSS will cost in terms of time-to-deployment and complexity of maintenance. It can take a hell of a lot of work to convince clients otherwise.

The story recounts a site redevelopment by ESPN, where the site was switched from table-based layout to a structured HTML and CSS-based layout. Mike Davidson of Newsvine has the whole story up at his blog.

This story has made digg today, which is where I found it. Not sure why or how, but digg’s a strange beast.

One Reply to “Why web standards DON’T suck”

  1. Ironically your site is having css problems. Some elements are overlapping in IE7. I still think web standards suck [proverbial c**k of life].

Leave a Reply