- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Mon, 2 May 2016 12:43:11 -0500
- To: "Rochford, John" <john.rochford@umassmed.edu>
- Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Hi John, Nice job! Thank you for writing this up. One thing that we may want to add is that CAPTCHAs may not only present distorted text visually but also distorted images. Check our Use Case Wiki page for sample linked images: https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Use_Case_Solutions#Fatigue Kindest Regards, Laura On 5/1/16, Rochford, John <john.rochford@umassmed.edu> wrote: > HI Jim and All, > > I have completed ACTION-52: Write "password" > need<https://www.w3.org/WAI/GL/low-vision-a11y-tf/track/actions/52>. I > decided to expand it because we are not yet addressing CAPTCHA and > 2-Factor. > > The text is below. Attached is the HTML to add to the user needs section of > the requirements > document<https://w3c.github.io/low-vision-a11y-tf/requirements.html#user-needs>. > I would have added it myself, but I don't have sufficient privileges. > > Authentication and Identity Confirmation > > Most user interfaces are designed to help users complete tasks. However, web > security and privacy technologies intentionally introduce barriers to task > completion. They require users to perceive more and to do more to complete > tasks. Three examples of these technologies are passwords, CAPTCHA, and > 2-Factor Authentication. > > * Passwords are words or character strings used for authentication > and/or for identity confirmation. > * CAPTCHA is a website widget, which 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; > * require users to enter that text into a field; and > * require users to invoke a submit button. > * 2-factor authentication requires a two-stage process to verify the > identity of a user. The user is required to have two of three of the > following factors: > * knowledge, e.g., password or PIN; > * possession, e.g., mobile device or credit card; > * inherence, e.g., fingerprint or voice print (via biometric > device). > > Challenges for People with Low Vision > > Web security and privacy technologies often block people with low vision who > may not be able to: > > * discern text they are required to enter and submit; > * recall text or instructions they have seen or heard; > * follow multi-step procedures. > > The scope of the problem is vast because, for examples, people with low > vision: > > * are prevented from purchasing goods and registering for services on > the millions of websites that employ web security and privacy technologies; > * may circumvent web security and privacy technologies with insecure > techniques/methods; > * may become so frustrated working through web security and privacy > technologies that they relinquish their efforts, and thereby are thwarted > from purchasing goods and registering for services; > * may be unable to become accustomed to a web security and privacy > technology because there are multiple versions of it across websites. > > User Need - Authentication: > > Easy-to-use web authentication and identity confirmation > John > > John Rochford<http://profiles.umassmed.edu/profiles/display/132901> > UMass Medical School/E.K. Shriver Center > Director, INDEX Program > Instructor, Family Medicine & Community Health > www.DisabilityInfo.org > Twitter: @ClearHelper<https://twitter.com/clearhelper> > > -- Laura L. Carlson
Received on Monday, 2 May 2016 17:43:38 UTC