No matter how many times you reason the case for web standards, there are some people who just don’t get it. They hide behind their ignorance as if it were knowledge, and the illusion of truth that they have created for themselves prevents them from opening their minds to the cold, hard evidence.
Today I was told that “standards are only useful when tempered with experience and testing”. What this actually says is “I don’t understand web standards. I’m out of my comfort zone. I’ll just do whatever appears to work for the browser I’m using and that’s the defacto standard”. Yeah, right.
Speaking as someone who (like many of you) has a whole load of experience specifically in building for the web, and who has done an enormous amount of testing across multiple platforms, multiple browsers and multiple years, I can categorically say that the easiest way of ensuring a consistently good user experience is to build using web standards. I’m not just saying it’s the ‘correct’ way, or the ‘best’ way or even the most fashionable way, but above all it’s the easiest way of reaching that goal. Where do these people think the recommendations came from? Were they just dreamed up as a method of making web professionals jump through hoops, or might they actually serve some useful purpose perhaps?
It’s all this hard-earned experience and testing has led me to work exclusively in XHTML and CSS for the last two and a half years or more. This results in the what I was told today boiling down to “web standards are only useful when tempered with web standards” – which is clearly ridiculous. Grrr.
On a slightly happier note, today we were pleased to welcome my new little neice to the world. Welcome to the world, Miram.



Comments
It kind of goes without saying doesn’t it? Just like every final product in every realm gets tested, it also is produced against certain standards for the best possible outcome (and so idiots can’t pass junk off as a good thing).
Of course, I have seen the opposite where unthinking mgrs. (mostly) just assume that the ”standard” will produce the best work automatically.
I tried to use a lot of the tools out there, but found that I was far better off doing it with a good editor and a generous assortment of O’Reilly books at hand. For a look at the result, see www.princetonacademy.org. Note that some of the content is driven by MovableType, but the design is all css, all the time.
This was my first site (other than my blog, which I have not taken any time to ”stylize”) and I am completely sold on web standards (thanks to guys like Eric Meyer and Jeffrey Zeldman, among others). Perhaps it’s because I was untainted with the tower-of-babble known as table-based design. Interestingly, as I’ve done a lot of view-source’s, I’m generally having trouble figuring out table-heavy designs.
Anyway, nice post and I completely agree.
...and I totally agree Drew. I am having a hard time with marketing types that think they can’t have the design they want with standard and accessible code.
Their problem is the techies near them don’t understand standards just ASP, .NET, and FrontPage. Oh and they curse Mac’s. I can’t believe that in an industry with such rapid change people seem to find a level of understanding then stop learning. ”No nothing new please, leave the boat alone and get out.”
Luckily I have the Ontarian’s with Disabilities Act (simaler to US section 508). It lacks any real teeth but it is a step in the right direction. I am just doing my 4th of many presentations to come on accessibility and standards on wednesday. Slowly they are coming around...
And congratulations.
To this end, I started coding with standards for everything I did quite rapidly late 2001.
Caused some upset on occaision amongst the other team members - mainly due to frustration at having to learn something ”different” - but they’re now taking an active interest and asking all sorts of questions.
I went from doing simply table-based stuff to average PHP-ability in quite a short space of time. The same is true of my XHTML and CSS skills - you just need a bit of time and the wish to learn.
Some people just aren’t open to change, and that’s what it comes down to. But we can all only do our part.
I guess my point is don’t worry about the shmucks - we’re part of a ”revolution” and some folks aren’t cut out to be revolutionary.
(Side note: I’m teaching a web design class - and incorporating standards so that there aren’t more ”bad” designers unleashed upon the internet - yay!)
All I wanted to do is replace an image mapped nav bar with a CSS styled text list. I tried explaining that it wouldn’t look much different, and pulled out the old ”text should be text” argument, but in the end I needed to just do it and show her.
She wasn’t all that impressed (I think she was feeling a bit out of her element and just didn’t want to admit it) but she had to concede the ease of making text updates in xhtml over cutting a new image every time.
The thing is, as much as I agree with you, some kind of middle ground needs to be found, I find so many developers and designers that are turned off by many folk’s aggressive push of Web standards. We all know it’s the right way to go, but I think the challenge now is to help people ”get” it without putting them on the defensive.
Using standards is only one aspect of designing a great site, application or online media campaign. Please don’t confuse bad design with the mere use of a table or two for, yes, tabular data.