#GAAD: On CAPTCHA

Today, May 16, is Global Accessibility Awareness Day. Its purpose is to increase awareness of and understanding around why sites and components of sites need to be accessible. Of course complete accessibility refers to much more, ensuring that all areas of life are available to persons with disabilities. But I think this day has a primary focus of digital and web accessibility. In that spirit, I want to show what can happen when the various accessibility issues have not fully been addressed.

I made a post way back in 2006 in Live Journal, (remember that? Almost 20 years ago now!) In this post, I railed against CAPTCHA, which stands for Completely Automated Public Turing Test to tell Computers and Humans Apart (Taken from This site.) First, that’s a mouthful. And second, it has been the vain of my existence since its inception. In those days, those of us who were totally blind were pretty much left out of the experience entirely. This meant that, for example, we could often not sign into websites that had put CAPTCHA in place, because we couldn’t “type the characters you see on the screen.”

Eventually, and I’m sure with a lot of elbow grease and advocacy, web developers began to understand that there were a significant number of individuals who were being barred from accessing their products because of this spam-fighting tool. So they answered the call by creating audio CAPTCHA, where words or numbers are spoken aloud, often with some kind of noise in the background to make it harder for computers to pick up what is being said. The voice is also usually not completely clear. And this works for a lot of totally blind people, meaning they are able to “pass the test” and get done whatever it is they are trying to accomplish.

The problem? What happens if you have little or no hearing and partial or total blindness. I am totally blind and significantly hard of hearing, so even the clearest spoken language can be hard for me to follow. If they deliberately make it hard to understand what is being said, I will be lucky to get, say, two of the five words they say correct.

I had this happen just yesterday. While trying to complete a recovery of my Microsoft Outlook account (I locked myself out because I couldn’t remember the password, another issue about which I could write an entire entry,) I encountered one of these lovely CAPTCHA. I switched from visual to audio and must have tried eight different sets of words before I gave up in frustration. I’ll have to get that sorted eventually, but at least I’m still receiving email to my account. I assume it will be lost if for some reason I log out of my Outlook.

Ovviously, this can cause much bigger issues if one cannot access a site that uses either visual or audio CAPTCHA, and as far as I know deafblind individuals don’t really have a way to get past it without sighted assistance. I did try to have some of the various AI solutions locate and read the characters on the screen, but I don’t think they are easy enough to discern.

I guess I’m wondering why we even use these methods, in the age of two-factor authentication. Maybe a code could be texted to a user’s phone? I know this would not be a complete solution as some folks do not have phones that can read text, but it would allow many more to have easy access.

Alternatively, I’ve seen some sites that ask relatively easy math questions for the person to solve to prove their humanity. Whatever the case, I hope people continue to be aware of this issue and the very real stumbling block it puts in some people’s path.

2 Responses to #GAAD: On CAPTCHA

Leave a Reply

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