A Practical Start to Web Standards

It’s been expressed to me in a number of ways that making the switch to web standards is a very difficult process, and difficult for many reasons. Let me outline a few of the views I have picked up on.

Problems

CSS can be strangely complicated at first glance (it’s a very different animal than HTML, JavaScript, etc.). And having to validate your XHTML? It’s like debugging a C script, isn’t it? I thought HTML was a markup language, not a programming language. The world of standards can be very threatening to the newcomer and the seasoned developer alike.

Convincing superiors/clients/coworkers to make the switch with you can be equally difficult, especially in an established environment. It’s the old “If it aint broke, don’t fix it” mentality, and while often trustworthy, it’s an all too common, and frankly dangerous, mindset.

Lastly, and in my opinion the only valid argument, learning everything to do with web standards takes time —- time I don’t have. Because I am insane, I actually enjoy spending a full workday creating websites, followed by a fun-filled evening of —- you guessed it —- creating websites. But every web professional can’t be expected to use their valuable free time to learn the latest-and-greatest methods, especially one whose real enjoyment of web design comes from the paycheck at the end of the week. (And there is nothing wrong with that motivation.) The trouble is that most businesses don’t have the capital or man-power to spend days on end tinkering with box-model hacks, image replacement techniques, and the like. And clients don’t have the patience (and rightfully so) to wait around for their hired professional to take time out from their job just to learn how to do it ‘right.’ It’s a vicious circle.

Suggestions

So, now that I’ve presented a few obstacles in the road to standardization, let me blaze a new trail around them (or at least leave some noticeable footprints).

When staring new languages/methods in the face, it’s always a good idea to step back and evaluate the situation. Make sure you understand why you agree with web standards. Specifically, it’s good to remember that ‘web standards’ is not specifically about validating XHTML or CSS or JavaScript or any other big buzz-word. What it is about is doing things in a logical, organized method which will (eventually, those new to CSS etc. will have to trust me) increase productivity, usability, and accessibility of your site.

So now that you’ve convinced yourself that web standards are the way to go, how do you convince others? I have to take myself back to the days of early programming. Good old BASIC. In playing around on my own, I began to develop the habit of using GOTO commands. Upon taking formal (as formal as you can get for high school) instruction, I was told that the use of GOTO commands was a very dirty habit, and one I should avoid in the future. My first reaction was to take offense. “How can you say that my work is wrong if it gets the job done? Don’t judge my methods!” Well, as it turns out, my GOTO commands got the job done, they just did it in a horribly messy way. It took some time, and some education on my part as to the ‘correct’ way to do things, but eventually I realized what my instructor meant. I could fully understand the benefits once I was able to utilize them. But it took time, and a bruised ego.

Changing peoples methodology is never easy. They will most likely take offense that you are ‘correcting them’ or ‘telling them they are wrong.’ And it very well could be that you are. If you run up against this type of resistance, my advice is to start off small. Baby steps. Start by introducing CSS as a way to manipulate fonts in your document. Maybe start to cut down on the nested tables. Eventually people will catch on, and when they do, progress has been made.

Similarly, if you just can’t find the time to learn, or your employer isn’t keen on the ‘Research Time,’ suggest you start off by redesigning the company website with web standards. If that’s too big (or too sensitive) of a job, than there is probably a smaller intranet site that could use a little remodel. Find things to do for your own company, things that can be picked-up and dropped at any given time. It’s usually the case that client work comes first, company work picks up the slack.

Conclusion

My conclusion for this article is simple. Start small. Don’t expect to make a Zen Garden entry overnight. Even if you can eliminate one <font> tag or layout-containing <table> from your page, you’re on your way.

Post and Author Info.

Published June 10, 2004 by:

This article is tagged with , , and .

Commenting is currently off for this post.
So far there are 12 comments.

12 comments

  1. I like your focus on semantics. Yes, standards are important, but they are a means to an end. It’s all too easy to forget.

    Loving the design too :)

    Matt Wilson Matt Wilson

    June 10th, 2004

  2. Absolutely excellent post.

    I get this sense sometimes that standards and most especially the full power of CSS are thought of as just another “niche” technology and are viewed by some as similar in feel to something like Java Applets, Shockwave, or even Flash – add-ons, plug-ins, or special technologies to extend the web. This view devalues the heart of web standards. What I think hasn’t hit the masses yet (and I mean the majority of web designers out there) is that logical and structurally sensible code can and should be the backbone of the web of today and tomorrow. The wasteland of tables and tag soup can be left behind (Please!). I’m just beginning to learn the real power offered by valid, logical code presented with structural XHTML and CSS, and though I fight browser inconsistencies I see the benefits of my lean code not just for now, but for later as well. I have much yet to learn, but I’m pushing myself to grasp this new thing for me. I go back now and wade through table based designs I created not even a year ago and it’s always the same. I have to swirl through so much markup to get to the meat and bones of my designs. It’s enough to make me barf after working with such elegance.

    I agree with you whole-heartedly. The approach kind of requires a slow build. Converting the entrenched masses can and will be touchy. Although I did win over my boss. One elegant stylesheet for our site redesign that allowed me to make sweeping design changes hit her like a sharp wind. A light came on. One trip to the Zen Garden opened up a whole new world. She was hooked. :)

    btw – i have really enjoyed the read. love the site…

    Christopher Bourque Christopher Bourque

    June 10th, 2004

  3. As a prima donna C/C++ programmer, I’d like to point out they they are “C Programs”, not “C Scripts”.

  4. Hi, I’ve been designing table-based websites since Netscape 2. I’m convinced of the power of CSS, I’ve got dozens of new design ideas in my head and in Photoshop.. But where do I start?
    I have been reading various blogs like Zeldman, Hicks, … over the past few months, I’m chewing on CSS Zen Garden examples, I’ve done it all, but I’m still looking for a simple introduction to CSS, preferably from the viewpoint of a table-based designer.

    At the moment I’m chewing trough the list in the above article, but if anyone could give me some pointers to the right articles, that might save me a lot of time!

  5. Thank you for this article. You are so very accurate and it is refreshing to hear a moderate viewpoint instead of the extremists (who are the most visible and therefore create the impression that they are the majority…they are not).

    Most of us have both real world requirements that essentially force us to follow a clients requirements, regardless of how much we try to convince them that “this is the right way”. Secondly, you have given me the inspiration to write an article on this very subject. I have been thinking about doing so for the last couple months, but feared I would not be taken seriously or my article would be of no “use” to the few that might read it. Why? Because I am not an well known expert on Web standards, usability, etc. And, the article isn’t an “opinion” that really should just be submitted to one of 1000 discussion groups. I do have a position on this issue and many others one encounters in the community (Fluid design or not!) by the way.

    But this article would focus on how opinions are actually formed, changed, influenced, etc. and the relevance that has to ones’ decision making process; this ultimately becomes a “solution” in the real world for your client.

    I have experience working for many years in a field called “Social Marketing” and the principles that guide the strategies and process in that field.

    What the heck am I talking about? Well, without actually writing the article here, I would briefly describe the practice of “SM” as the process of influencing (and understanding) how people form opinions on social issues (like Reproductive Health or the Death Penalty). Basically, it is how to “win”, but not by selling more Pepsi, but my moving a social issue forward (through the various bumps in the road).

    I thought that part of my career had no connection to my current profession (front end Web specialist/Web designer…) but I see amazing similarities in this industry and the issues that are so important to it currently.

    I think the “SM” principles apply to us as well (much to my pleasure). BTW, these are principles that have been tested, studied, played out for many decades and have substantial validity. The one example I gave about “extremists being the most vocal and appearing as the majority is an example. But to give you a taste of what the big picture is, they are also very important because they serve the function of making the rest of us appear very reasonable, even if we are basically on their “side” (by “extremist” I refer to opinion only, not actions of violence or terrorism).

    This, and a dozen other interesting principles, apply to our field as well; because knowledge of how people are “moved” on an issue is crucial in our process of forming our own opinions, or practices, determining what is a preference or a real guideline, and relevant to the bigger picture: A relatively new profession is attempting to establish a set of guidelines, standards, rules, whatever you want to call them, while at the same time still learning about this great new medium, the Web.

    Thanks again, Michael

  6. A very nice and informative post. Feels like what u say , U mean it. Resistance is always encountered when one triggers change. Only after understadning the benifits of change required 100% efficiency in new methods cannot be achieved.
    Keep Posting Good things.

  7. I agree with you whole heartedly. I started this at a small page first and then migrated every page .

    Thanks for the good write up !

  8. Someone once said that web standards are just a big stick used to hit web designers.

    But there are many compelling reasons for Web Standards. Here in Australia – we have the DDA (Disability Discrimination Act) – which makes it law to have an accessible website. And ‘accessible’ is generally equated with Standards based design and W3C validation.

    Aside from the legal issues – two other compelling reasons I can add for web standards are commercial. Search Engines index words – and having valid code, and semantically correct code – helps your search engine ranking – as your content is easily indexed and the meaning is better understood. And reducing ‘code bloat’ – through the separation of content and presentation – reduces hosting traffic charges.

    Here is an overview of some other website accessibility concepts which should also be considered as part of the ‘trend’ towards standards based design.

  9. @Lode:
    If you want to ‘convert’ from tables to XHTML + CSS, I can recommend “Eric Meyer on CSS” (+ probably a CSS reference guide).
    I started out that way… and it worked great for me.

  10. I spent way too much time trying to learn how to build with xhtml and css. Yes, the eric myer books are ok, but I have yet to find a solid web design resource that tells you what you really need to know to build a clean, cutting edge site.

    The best book so far Is web standards solutions, by Dan Cedarholm. It’s clean, concise, and will get you on your way. I read it and it helped me learn the basics.

    Then I just viewed the source code of sites and followed trails to the css files and graphics to see how they were built. That is the best way to learn until someone comes out with a book that can teach how to build nice sites.

    mattmikulla mattmikulla

    October 25th, 2004

  11. I’ve been so passionate about adding CSS capabilities ever since my first web design course. Ever since then, I’ve improved and have been working for little organizations around my school. However, I must also say that I’ve been hooked on learning how to design with web standards ever since I’ve been reading blogs (Zeldman, Cederholm, Hicks, Didier, Shea and now yours – thAnkS!).

    I believe you really described the problems behind standards and even using css while working with organizations. I’m currently working for this organization, and the person above me is obsessed with using nested tables, and believes CSS is evil. He won’t let me touch any of the code at all, even though he keeps adding endless code that makes it impossible to work with, let alone usable to the people that use it everyday.

    Convincing about the power of CSS is absolutely challenging, and I thank you for bringing that up. It’s refreshing knowing that people do feel the same way.
    Any more tips on convincing clients to move to CSS and web standards, let me know. I can surely use it, especially when writing my proposal for one of my classes. (Please feel free to email me too. I like emails…or you could write an article about it too!) haha…

    Well thanks again… i’m going to print this article out now and place it in my binder of web goodies…

    -=)

    Ryan

  12. Hi hunters! This site for you! All for a successful hunt! Now! http://www.hunter-online-store.info