Web Standards Are Your Responsibility

Last week my post Standards Geeks Hard To Come By raised some good discussion. One of the threads I found particularly interesting is the age old tale of how many developers, for a host of reasons, cannot use Web standards in their day job.

At the risk of pissing some people off, I'm going to call bullshit on this one. This goes out to professional Web designers and developers everywhere: Web standards are your responsibility, even though you might not know it.

I know, probably better than many, how much of a challenge Web standards can be to implement on a day-to-day basis. I've expressed my angst towards standards and validation in particular many, many times, but when all is said and done the only way I've been able to use standards on my paying projects is because I pushed long and hard for them and probably spent many an extra hour of my own time making sure Web standards were a part of my projects.

Standards can be hard, but they're not impossible

I can name quite a few reasons why people would have trouble making the move toward Web standards in their daily work:
Next Page

(c)Copyright 2024 BlueValve.net. All rights reserved.
Unauthorized duplication in part or whole strictly prohibited by international copyright law.