Addam Wassel's Blogging Adventure

bbc vegas sports travel tigers womma michigan wedding design typography football internet encoding myspace chicago weather stupid thing i did tea fire el dc moving newsvine editing podcast music books amazon round cube food my web odeo icon buffet trash bags ann arbor ruby on rails laptop geek lifehack chores iron internet explorer canoe movie animation disney css web standards disaster hurricane computer baseball england olympics holiday basketball softball superstition meme graduation ipod art exhibit open mic tagging mashup review html working group w3c npr this american life html5 rant

Over the long weekend, a debate started that completely flew under my radar! I might be slipping in my older age... Anyways, it's seems approriate to me, at this time, as the launch of our 5.0 storefront is coming this week (fingers-crossed). And we've battled mightily with IT the whole way.

Our IT department was stuck in 1996's table based design up front with 2010's XSLT on the back. There was no transitioning between. Luckily, John showed up. He was our pied piper of sorts, leading the charge for CSS integration into the new site.

I would complete agree that it is up to the designer to create accessible content. But there have been times, in the redesign of our site, where our IT department just can't - or won't - do something that was coded in CSS. They constantly revert back to their table-based designs. It's then up to us to figure out a way to fix that.

Now, admittedly, I haven't had much of a hand in the actual redesign. In fact, it's been very minimal, but that doesn't mean I haven't heard the horror stories of our IT department. (One of which being that, because they are using Microsoft’s .net technology coding ID's in the XHTML isn't doable. Apparently, .net’s architecture automatically enters an ID on it's own or overwrites any existing ID's, making the new storefront consist of only classes.) IT have even told us that CSS layouts were unacceptable and that we needed to go back to coding with tables.

I think it's up to us, being the standards geeks we are, to show the outside would the advantages of CSS-based designs. Less markup means less load on the server which equates to saving the company money, ease of updating the site - be it for a redesign or a minor color tweak, and probably the best reason is that using standards, there is a better base to jump off for accessible sites that will come down the road.

I still believe it is my job, be it in freelance or in the office to push for standards based design. Developers will (hopefully) appreciate the clean code I send their way and future designers will appreciate the ease of editing my sites. It's the designer's job to be informed about these topics. And hopefully, they won’t have a battle with the IT department to implement them.

Be the First to Comment

Visit WasselDesign.com

Copyright © 2005-2007 Addam Wassel. All rights reserved.
XHTML, CSS, RSS feed. Powered by Movable Type. Hosted by (mt) MediaTemple.