We're Just Temporarily Abled

We aren’t just designing accessible products and websites for a subgroup of people who we may or may not know, who have permanent visual or motor issues. We’re designing these sites and products for our future selves as well.

Article No :1634 | June 10, 2016 | by Jennifer Aldrich

A few years ago, I had the opportunity to attend and present at a great conference where Cindy Li delivered a phenomenal keynote.

I learned about 8 million new things during her talk, but she made one particular statement that really stuck with me.

She simply said,

“We’re all just temporarily abled.”

She talked a little bit about her mother who has an ocular disease that is slowly blinding her over time. Then she mentioned that while she doesn’t have an ocular disease herself, she is beginning to require stronger glasses prescriptions each year.

Why am I talking about Cindy’s eye health? Because she then pointed out that as designers we need to design for accessibility, not only for folks who are permanently visually or hearing impaired or have severe motor issues right now, but also for our future selves.

Design for the future you.

With each passing birthday, our vision is starting to go. Eventually our hearing will start to go and so will our mobility. I will have these issues, you will have these issues--they’re just part of the aging process.

We aren’t just designing accessible products and websites for a subgroup of people who we may or may not know, who have permanent visual or motor issues. We’re designing these sites and products for our future selves as well.

The next time you’re tempted to brush off accessibility while you’re working on a design, picture yourself in 20 or 30 years trying to use your own website or product. It’s a pretty life changing shift in thinking. I like to call it “forced empathy.”

Angry, sobbing or drunk people may try to use your product or website—ready?

The last day of the conference, a second session was held that had a focus on accessibility. This time, the presenter, Robin Smail, pointed out that every visitor who comes to your site is NOT going to be dedicating 100% of their mental energy to navigating your product or website content.

What if they just fought with a family member or coworker? They are going to be smashing their mouse around on the desk trying to get through your product or site. What if they’ve been crying? Their vision is going to be impaired. What if they’ve been drinking? (I’m sure YOU have never shopped online while slightly intoxicated, but you know… OTHER people do it.) ;)

The point of her talk was that we need to focus on accessibility and awesome UX for ALL visitors, whether they have permanent issues, or temporary ones.

Pitching Accessibility Focus to Stakeholders

I’ve been chatting with friends in the industry about designing with accessibility in mind quite a bit lately, and I keep hearing the same story over and over again. They are having a very difficult time getting stakeholders onboard. Stakeholders seem to often treat accessibility like it’s a dirty word.

Some common responses seem to be:

“We don’t have time for that.”

“We don’t have a budget for that.”

“Most of our customers don’t need it, why bother?”

If you run into a wall when trying to pitch accessibility testing and optimization to stakeholders, try putting the temporarily abled spin on it.

It shouldn’t be necessary, since making websites and products accessible is exceptionally important, but sometimes forcing someone to envision the work helping them personally can really go a long way. It helps shift the thinking from making design changes for “those people” to making design changes for “us”. It’s unfortunate, because making that designation shouldn’t even be part of the decision making process—it’s just the right thing to do, but when you’re up against a wall of resistance that change in mindset can make a huge impact.

Another great way to get them on board once you’ve had he temporarily abled conversation, is to show them what it’s like to navigate their site or product with a screen reader. (Spoiler alert: It may make them want to gouge their eardrums out with pencils.) Folks often don’t realize what they’re putting other people through by not making their sites and products accessible. A quick demo can be very eye opening.

Accessibility Testing Tools:

I had no idea where to even begin when it came to accessibility testing, so over time I’ve built out a small list that will help get you started:

I’m not even remotely close to being an accessibility testing expert, but there are tons of people who are. If you are knowledgeable on the subject, please share your insights, tool recommendations and article links with the design community. And if you’re knowledgeable but haven’t written any articles yet, please consider doing so! The more exposure we can give to the importance of accessibility testing, the better.

About the Author(s)

Jennifer Aldrich is a UX & Content Strategist at InVision and UX Blogger at UserExperienceRocks.com. She's a fan of: her daughter, photography, writing, and beautiful usable things. She'd love to connect with you on Twitter!

Comments

Emmanuel

August 8, 2017

Hello Jennifer, do you remember the name/place/date of the conference you are talking about? I haven't find it. Is there any online resource of this conference (video, slides, etc.)? Thank you for answering.

Graham W Ayre

July 27, 2016

Nice article. I have always been a keen follower of accessibility, and I do like seeing more awareness of it across the web. Another colour contract tool I use is snook

I have also trialed JAWS software blindfolded, and recommend designers and devs to try it out themselves. It certainly makes you more aware of your actions and how you can improve the online experience for a wider audience. A read a interesting article by David Ball in regards to lessons learned after participating in this type of experience, source:

Great article, I love the style it is written. I agree with the author!

Cameron

June 10, 2016

Great article Jennifer!

I am a UX designer for a small software vendor that does a lot of business with the federal government. When I first started my gig at the company, my primary goal was to ensure that our products were Section 508 compliant. This took a whole lot of research, testing, and selling the importance of accessible technology to various people.

I like your list of testing tools. I find the WAVE evaluation tool to be of particular use. I also test our software with JAWS and Apple VoiceOver. I do feel like I could write an article regarding my accessibility-testing workflow as well as other related methods I have used.

Again, very good read!

Dave Linabury

June 16, 2016

We ued JAWS as well. Not sure of the agency still holds to this, but initially, we had every developer and IA surf the web blindfolded using JAWS to see what it was like. Gives you a deep respect for the Skip Nav link!