oz: the blog of glenda sims ( the goodwitch)
Toto, I've a feeling we're not in Kansas anymore.
What are you doing May 11-12? I hope you are attending Access U in Austin, Texas! What is Access U? A two-day accessibility conference for webmasters to teach you both the how and the why of creating web sites that meet federal, state, and industry mandates for accessibility.
Attend AccessU for:
What is it about SXSW Interactive? It is just a conference after all. But honestly, it is unlike any other conference I attend. It is simultaneously visionary and insane, brilliant and ridiculous, inspiring and intoxicating. And it dawned on me that whoever named this conference nailed it. The whole point is to interact with each other. To share your wildest dreams, ask preposterous questions, make and renew scintillating friendships.
I love to share my passion for accessibility. There is something incredibly satisifying about kicking down barriers to information. I’m inspired by the goals of the W3C, “Web for everyone. Web on everything.”
With this in mind, I wanted to share my own practical accessibility practice. When asked to test a site for accessibility, these are the steps that Glenda the Goodwitch takes:
When it comes to usability and information architecture, there is just no replacement for a good search engine on your site. Try as you might to design an intuitive navigation scheme, let’s face it…one size never fits all. But no need to fear…your search engine can add an alternative way for folks to find what they so desparately seek.
In my world (UT Austin), I’ve got two obvious choices for search engines, Google Free University Search and htdig. While Google is sweet, I can’t customize the results page, so google doesn’t meet my needs. So, I turn to my good ole friend, htdig. But unlike other sites where I’ve implemented htdig, the site I’m working with now stretches across two different servers and is virtually hosted as well. Creating the results page header and footer proved to be a challenge because (horrors), htdig wouldn’t let me use server side includes (ssi) . Ouch!
I toyed with the idea of writing the results page in PHP but was convinced that if I thought creatively enough, I could trick htdig into letting me use ssi. And after a few bumps and bruises I won the battle. So, in case you’ve got a yearnin’ for ssi in your htdig results page, here is what I learned yesterday.
Are you a lean, mean design machine? Do you long for the opportunity to design web sites the way you know they should be: accessible, usable and standards complaint? Does your organization care more about cheap, fast results rather than quality code? Then it is high time for a web wrestling smack down in SXSW style!
I’m curious. When designing sites using css layout is there value in setting a bar for browsers you’ll bend over backwards for? Is there ever a point where it is okay to say, “I’ll design for standards complaint browsers, and I’ll even degrade gracefully down to a point…but past that point, I’ll strip the css… Continue reading How Low Do You Go?
Imagine my surprise, when I pointed my PDA browser (Pocket Internet Explorer aka PIE, Mozilla/4.0 (compatible; MSIE 4.01; Windows CE; PPC; 240×320)) to www.cnet.com and my browser crashed! Ouch. There seems to be a bug in my PIE!
I couldn’t resist lifting up the hood to see if I could identify the culprit.
XHTML 1.0 Strict is my new best friend. Designing pages using this doctype is the perfect new year’s resolution to ensure that my site is slim and trim.
So, we could get into the argument about whether HTML 4.01 Strict is better than XHTML 1.0 Transitional, but personally I think that argument is not worth having until you can tell me why you are not adopting the W3C standard of XHTML 1.0 Strict.
Here are the reasons I’m choosing XHTML 1.0 Strict: