Towards a standards compliant web?
February 18th, 2007
Web standards advocates Shari and Aja are looking into forming a group of like minded people — that is, web standard advocates — and I wish them luck in their endeavors. I’ve never been an advocate, although I loathe the use of tables myself, but it’s more of a practical matter: I find divs just easier to code than tds.
[UPDATED - sorry Shari, I had my WP set to auto publish when saving, but I was still writing this when you posted your comment. Please feel free to double post.]
One trepidation I’ve always had with this kind of thing, however, is that often the means become the ends. It reminds me of the old design vs. content tiff in that sense, where both sides seem to forget that good design invariably means having good content, and vice versa. I should know the arguments; I was on more than one side at certain points! Egads. Seeing those sites now is painful, to say the least. Partly because I’ve since lost access to them, and partly because some of those were just downright awful to look at
One thing I have against standards compliant code is that, despite claims otherwise, it’s not easy for most to adjust to, particularly if you’ve gotten used to Imageready’s slice and export. I know some absolutely amazing designers that don’t know their way around code or CSS, and it’s not easy to instill in them a sense of why it’s important for their code to be machine readable as well as pretty to look at. And I can’t really blame them: they design for people, and web standards are, invariably, for machines. Sure they make my coding life easier, but really, until CSS3 comes along and the folks at Microsoft get their act together, is it really worth the hassle?
Henri de Toulouse-Lautrec once said: In our time there are many artists who do something because it is new; they see their value and their justification in this newness. They are deceiving themselves; novelty is seldom the essential. This has to do with one thing only; making a subject better from its intrinsic nature. What is the essential, then, in websites? I would posit: the content. What is a website’s intrinsic nature? To provide said content. Do web standards make the content better?
Let me rephrase that: from a non SEO, purely human standpoint, do web standards make the content better?
I say it doesn’t do a darn thing to the content unless you happen to blog about web standards. But that’s a trick question: in this day and age, is there such a thing as a non SEO, purely human standpoint? There’s not. It’s a problem for today’s blogger that even the way you write titles must be considered for their Digg-ability and Google ranking. Misplaced zeal over the semantic web has taken the focus away from humans, and it’s a problem that can be seen with a lot of blogs that only write about the latest high-paying keyword. And yes, this is the kettle calling the pot black here, because I’ve written more than my fair share of bad content, although I can’t linkbait worth a damn. I don’t like it, but it’s true nonetheless. The ends and the means have been confused and mixed up too much. To borrow from Richard Lovelace, SEO practices do not a good website make, nor standards compliance good content. Content makes content makes content.
But it does make for an easier time writing. The success of Blogger and Wordpress are proof of that. And there is a certain quality to quantity. I just can’t help but notice the blogs with nothing really unique, relevant or personal to say, but instead contain a dozen links per post to, you guessed it, keywords. The net effect is that weak content has actually grown in proportion to good content.
Am I blurring the lines between SEO and standards compliance? Yes I am, but with good reason. The two go hand in hand; after all, isn’t good SERP placement one of the selling points of the semantic web? SEO sells, and standards compliant code is one of the best (white hat) SEO practices out there.
That said, I think the semantic web is a good thing. I applaud the initiative of people like Aja and Shari, precisely because their sites are good examples of a successful marriage between good content and standards compliance. They are role models, if you will, and while they are not alone, they are still too few. That’s why I support what they want to do, because I think it’s a good start towards a better web. For machines and humans.





February 18th, 2007 at 4:25 pm
Why only wish us luck when you can join?
But thanks for plugging us anyway.
Truth is, I’ve never been a fan of table layouts myself. I agree with you that divs are easier to code than tables. I can’t even imagine how the others manage to do them. o_O
I do advocate web standards, but I most certainly won’t die of annoyance and/or anger just because someone chooses to not go by the standards. (Although I admit that I dislike the typical bright pink layouts of Pinays proliferating the web so much that sometimes I even look at their codes critically just to find more faults, lol)
February 18th, 2007 at 7:28 pm
I dunno, I like pink ^_^ LOL. I know what you mean about other people’s table wizardry — I get lost after the first nested td, and don’t even get me started with numrows >.< Use it for tabular data, I say! As for joining, well, let’s just say I’ll be the first to subscribe to your feeds when you finally get it off the ground
I had my WP set to auto publish when I saved, so your comment came before I remembered to put this on draft because it wasn’t done yet. Please feel free to double post
February 18th, 2007 at 8:40 pm
Aha! So someone else made the (kinda similar) mistake I made. ^_^ My post was only about a quarter done coz it’s supposed to be just a draft for tomorrow today’s entry, but I guess I was too sleepy to notice that I must’ve published it. That’s why it doesn’t make much sense. And I’m too lazy to edit it. Boo.
I hate pink though I really don’t mind it much. But gosh, 90% of Pinoy blog sites are in pink! I mean, can’t they use any other color? Geesh. As for tables, same here. They make me dizzy. @_@
Anyways!
Personally, I don’t mind looking at badly-designed websites, which I don’t really see much of. I’ve always been more of a “content is king” person. With all honesty, I see very beautiful, artistically done websites, with so very baaaaaaaaad coding that I have to use one despicable web browser we shall simply call by the codename Miscrosoft Internet Explorer to view the sites properly. By promoting web standards, we’re actually trying to eliminate the browser problems that might arise with improper coding of sites. We’re not taking away the “design” concept here. I agree, web standards doesn’t make better content, but hey, let’s not even start on those people who take advantage of it to get to Google’s #1 as their personal mission. :p I may be a little disappointed that the means and the ends are mixed up, but with the web standards group we have in mind, we’re focusing more on web usability and accessibility rather than search engine optimization. “Better web” means better web for humans and machines, as you’ve pointed out, thank you.
So sali ka na.
I know I’m a bad designer myself, so I try to focus on what I can do better: coding. And, maybe, even content. Okay, I kid myself. ^_^ But thank you. I’m really touched with what you’ve written, lalo na yung last paragraph. Nyahehehe.
February 19th, 2007 at 11:03 am
Natawa nga ako kasi I was just reading that post of yours where you said it was supposed to be a draft only - tapos ginawa ko din T_T
Best of luck sa project nyo! I’m ambivalent sa joining because I don’t have much to offer