• Their clients, stakeholders and coworkers don't know about, or care about, Web standards.
• They feel they can't adequately support legacy browsers.
• The learning curve, with CSS in particular, can be high.
• They don't get paid any more to add the added responsibility of standards (and validation) to their job descriptions.
• They feel more comfortable with legacy coding techniques.
• The initial conversion to standards-based markup can be a humongous task.
• They are annoyed by the endless preaching of standards advocates… ;0)

I could go on, but I want to be clear that I understand the challenges involved. But as my mother used to say to me, “Can't never did anything.” I was able to bring standards to my projects at Boeing and then again to Children's (where they've since jumped fully on the bandwagon and are currently looking for a developer) and while I had help, I also had quite a few of the challenges mentioned above.

If I could do it at Boeing, you can do it at your job.

What they don't know won't hurt them

One of the most common, well, let's call them excuses, is that clients don't know or won't pay for standards. Big whup Next Page