We Haven’t Forgotten About Accessibility, Have We?

Back when Web standards were the talk of the town, accessibility concerns were a hot topic of conversation as well. After all, the accessible nature of Web standards was a good argument to those that didn’t stand behind standards, right? Lately I’ve been fearing that we may have in part lost sight of how truly important accessibility is.

I watched a screencast the other day, focused on experiencing Twitter through a screen reader. If you’ve got a spare 3 minutes, check it out:

The Screenreader Experience Part One from NAPCS on Vimeo.

I was gritting my teeth not only at the frustrating user experience, but at the fact that I know I’ve unconsciously let a few best practices slip when working on recent projects. As stated in the screencast, I’m not trying to pick on Twitter, as I think we can all agree that accessibility sometimes takes a back seat in favor of new hotness.

Accessibility is more than standards

Watching that screencast brought me back to an internal debate I’ve been having for some time. It seems as though advanced interactions on the Web — JavaScript, HTML5, and otherwise — becoming more prevalent may have us a bit blinded to the underlying importance of making our sites accessible.

If I had to venture a guess, I’d say that the majority of us have never had a one-on-one experience with a screen reader. The leading software is pricey and it runs on Windows. It therefore has a general barrier to entry for the majority of us. There are alternatives, but we as designers realize the importance of using a piece of software in its natural environment. We test in more browsers than we would ever want to, but we do it because we’re professionals and we take pride in our work. That said, we should be testing assistive technology as well, but we don’t.

Is the world moving on, again?

There are more inaccessible, downright bad documents floating around the Web than I care to think about, some created very recently too. I’m hopeful that the world hasn’t forgotten about accessibility, but things like Google pushing the capability to crawl AJAX applications really facilitates bad practice, in my opinion.

I’m not trying to knock Google for doing what it does, but in all honesty the fact that Google didn’t index AJAX-powered applications was one of the last remaining reasons for developers to take accessibility seriously. That’s not to say that AJAX-powered applications can’t be accessible, it just opens the doors to leave the principle on a back burner.

Accessibility received a ton of attention during the ‘original’ standards movement, and I look upon that very fondly. I learned a lot during that era, but unfortunately I’ve forgotten to retain those best practices from time to time. That’s something I’m going to focus on quite heavily in an effort to retrain myself, maybe you can too.