If you are interested in real world, proven interpretations of the WCAG guidelines, check out this site today.

It’s cool.

How do I know about this fascinating book, you ask? Because Jeremy asked me to be a technical reviewer of his manifesto. And I agreed, having nothing but total disregard for my pet projects and their timelines. If I don’t launch, they can’t be criticized, unless you can see inside my brain. You don’t want to look there, it is dark, dank, and inaccessible in there, unlike Mr. Sydik’s book. The book is bright and shiny and contains many useful and practical insights into the concerns of the disabled and practical approaches to addressing those concerns.

Kudos, Jeremy! I don’t know what kudos are, and I’m too lazy to google it. You should have truckloads of them, though, for having the talent, persistence and foresight to write this book and get it published. Huzza!

Enough Monty Burns talk. On with your day! Nothing to see here, please move along.

First off, in the spirit of the never-ending redesign, here’s a great 15 tips blog post on choosing a type face. I am a type amateur, but I love reading and learning about it. This Spiegel article is ancient in our 24/7 newscycle, but here’s a community that has done away with traffic signals. This is reflective of Christopher Alexander’s maxim to always design scaled to the user. It also shows how, though human-designed systems are good, human nodes in an amazing complex physical, emotional, and spiritual system called the world possess an innate ability to regulate themselves and their behaviors absent the enforcement of other humans. Libertarian moment over… now.

From a time slightly after the Spiegel article came out, i.e.—right after the dinosaurs started becoming oil—Tim O’Reilly felt compelled to redefine Web2.0 with a more compact definition. It’s a good read, but the Hype Curve has sailed on that one, Tim.

Some random accessibility stuff about video captioning, Dutch law and a new effort by Joe Clark to make media uniformly accessible.

Garrett Dimon has an interesting article about markup as craft. I’m pessimistic today, so all craft feels dead to me. Happy Valentine’s Day. However, Garrett’s 21 points are right on. They’re the implementation details of these 15 research article-derived design tips. What the heck is up with 15 being the magic number of tips? Who the heck knows?

Where did I get all this great stuff? Lots of it came from the Web Standards Group mailing list. This maxdesign guy put out the links for light reading weekly. Highly recommended.

In the file under random portion of our post, I’m beginning to research buying a hybrid, and this Jamis Buck article on concerns in activerecord in Rails hit the spot, oh, a month ago, when I began this post, back when my life was far less chaotic.

One of the ways in which accessibility work can help your organization better understand its products and services is in defining usage scenarios and task flows to consume those services. Abstracting away the peculiarities of an interface—be it web 1.0 or AJAX, voice or kiosk—requires you to understand the process and factors that impact task completion and satisfaction.
I’ve been playing with the idea of what I call an “equivalence matrix” to represent different contexts, modes, and scenarios in which a task may be completed. In an ideal world, you’d have a taskflow, let’s say ‘pay the cable bill’. In the matrix, for each persona you’d have a scenario and distinct, use case information about how they would complete the task. If you already had existing use cases, this would become a fill in the blanks exercise for the new personas you’re considering, in this case, that of people with disabilities or technological limitations.

This idea sounded much better a cup of coffee ago, but I’m letting it into the wild anyway. Anyone ever dealt with this? Done something like it? Drop a comment and let me know…