validators and Songs Ohia

So I’ve been spending probably more time at work than I’d like to admit playing with the W3’s (x)html validator. I got all excited when I found out the default movable type templates validate, and started converting my old static pages to css layout (most are still using font tags), and writing them to validate at the same time.

Then I randomly ran into this accessibility tutorial that just kicks ass, and I’ve been trying to integrate that information too. Probably the most interesting part of that tutorial is how it says who benefits from each tip, and one of the “people” who can benefit is google. I had no idea, but yes, many accessibility tips will also increase your site’s rapport with google.

I want my pages to look good in text browsers like lynx (which can check with this handy Lynx Viewer–although I’m not sure why anyone would use lynx when w3m is so much better. ;) and many of the changes for text browsers are pretty much the same ones that need to be made for accessibility, so that’s nice. Fortunately, back when I handcoded most of those old pages, as clueless as I was, I still tried to keep things as simple as possible. So the work is mostly doing things like closing paragraph tags (I still thought of paragraph tags as just adding space between text) and un-nesting various formatting tags (like center and blockquote).

It’s fun, actually, to revisit these pages, revamp them a little. I like the new stylesheet I’m using, I might make this one a little more like the one I’m using there.

Oh yeah, I almost forgot, Songs Ohia is at first ave tonight. I might have to skip unicycling again. I haven’t decided.

Leave a Reply

Your email address will not be published. Required fields are marked *