Re: web-security technologies, CAPTCHA, v1

Dear John, All:

This is a brief FYI to let the COGA TF know about an existing W3C
publication about accessibility issues with captcha:

http://www.w3.org/TR/turingtest

As this document is almost a decade old now, it's overdue for updating,
and it is PF's intent to update it. Unfortunately, competing priorities
have prevented us from moving forward on an update so far, but I do
think we'll be taking this up in 2015.

Janina

Rochford, John writes:
> Hi All,
> 
> As you may know, I agreed to review web-security technologies. I chose to begin with CAPTCHA. My first draft is below. The format I am using is the one I intend to use for future reviews. All the text is my own.
> 
> I welcome your feedback, additions, and/or revisions.
> 
> CAPTCHA
> 
> Definition
> CAPTCHA is typically a website widget that prevents automated programs from submitting a web form intended for humans by requiring humans to pass a test. Such tests present distorted text visually and/or aurally; and require the form-submitter to enter that text into a field, and invoke a submit button.
> See http://www.captcha.net/
> 
> Problem
> CAPTCHA often blocks people with physical and cognitive disabilities who cannot discern the text they are required to enter and submit. The scope of the problem is vast because, for example, people with disabilities are prevented from purchasing goods and registering for services on millions of websites.
> 
> People with Cognitive Disabilities May Not Be Able to:
> 
> *     read CAPTCHA text at all because of the intentional distortion of it
> 
> *     comprehend text that can't be enlarged without additional distortion
> 
> *     have the advantage of comprehending the meaning of words or images
> 
> *     understand text spoken in a computerized and distorted voice
> 
> *     complete the multi-step procedure for submitting the CAPTCHA text
> 
> *     complete a timed CAPTCHA due to slowness in completing all steps
> 
> *     understand the purpose of buttons such as reset, listen, and help
> 
> *     recognize functional elements, such as buttons, are clickable
> 
> *     focus due to irrelevant instructions such as "stop spam" and "read books"
> 
> *     become accustomed to CAPTCHA because there are multiple versions of it
> 
> Alternatives
> 
> *     Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web<http://www.w3.org/TR/turingtest/>, World Wide Web Consortium, November, 2005.
> 
> *     A Sliding Alternative to CAPTCHA?<http://www.lukew.com/ff/entry.asp?1138>, L. Wroblewski, June, 2010.
> 
> *     sweetCaptcha: Fun and Human Friendly Captcha<http://sweetcaptcha.com/>
> 
> John
> 
> John Rochford
> UMass Medical School/E.K. Shriver Center
> Director, INDEX Program
> Instructor, Family Medicine & Community Health
> http://www.DisabilityInfo.org<http://www.disabilityinfo.org/>
> Twitter: @ClearHelper
> 

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

Received on Tuesday, 2 September 2014 13:11:03 UTC