W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

RE: example of accessible captcha?

From: Karen Lewellen <klewellen@shellworld.net>
Date: Tue, 31 Jan 2017 19:58:56 -0500 (EST)
To: "Sean Murphy (seanmmur)" <seanmmur@cisco.com>
cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.64.1701311955130.8745@server2.shellworld.net>
Well, at the risk of singing the same song again, a shared label does not 
a shared experience make.
That you do not find an task difficult is absolutely fantastic...for you.
It does not mean everyone within the same well label has your tools your 
situations, or choices.
I was frankly stunned that assurance could get away with such a clear 
problem. I Mean what if the person has another reading  challenge?
Kicking them out because they cannot read when providing phones that have 
no access at all is a tad much.

On Tue, 31 Jan 2017, Sean Murphy (seanmmur) wrote:

> Interesting, point in relation to text messages. AS I have vision loss myself, I didn't find it difficult.
> As there are more and more organisations using this as part of their security mechanism. One example that comes to mind is two step authentication. I suspect the challenge the example you provided is related to the assistive technology they had available on the mobile device. If the technology doesn't permit them to read text messages easily, then the solution will break for that group of users. Thus isn't full proof.
> The other ideas promoted I need to check out. As this is really a pain point for accessibility and disable users.
> Sean Murphy
> Accessibility Software engineer
> -----Original Message-----
> From: Karen Lewellen [mailto:klewellen@shellworld.net]
> Sent: Wednesday, 1 February 2017 10:28 AM
> To: Sean Murphy (seanmmur) <seanmmur@cisco.com>
> Cc: w3c-wai-ig@w3.org
> Subject: RE: example of accessible captcha?
> Hi sean,
> I personally dislike the text message idea for two reasons.
> first, you must provide your cell number, which if the site in question becomes compromised  creates issues.
> second and most important though that method assumes that both a phone  is available, and a phone with easy to access text messaging.
> I knew someone experiencing sight loss who got kicked out of the low cost American cell phone  program because their provider called assurance wireless  used  text messages to contact members.  The phone provided in the program had no accessible features so...they lost their service because they could not  read the screen.
> I believe Google is behind recaptcha.  If they no longer encourage the visual captcha, then recaptcha should not create as much.
> I agree totally with you about the audio editions of the challenges for many reasons.  those are a poor solution  in my experiences as well.
> Kare
> On Tue, 31 Jan 2017, Sean Murphy (seanmmur) wrote:
>> Karen,
>> I like the concept of sites which use text messages that appear on your phone. Then you enter in the number they provide as the challenge.
>> Audio caption solutions in my book are a negative experience because if you cannot understand the audio output. Then you cannot complete the form. As most audio challenges are distorted audio in the first place. I and quite a lot of others find this method of authentication very poor. This is of course to address the vision impairment community who cannot se the challenge graphic.
>> There was an article I read ages ago where I think google had
>> developed a method of not requiring the graphical challenge at all and
>> used a completely different method. I went looking for the article and
>> cannot find it. :-)
>> Sean Murphy
>> Accessibility Software engineer
>> -----Original Message-----
>> From: Karen Lewellen [mailto:klewellen@shellworld.net]
>> Sent: Wednesday, 1 February 2017 6:12 AM
>> To: w3c-wai-ig@w3.org
>> Subject: example of accessible captcha?
>> Greetings all,
>> I seek a site that uses a captcha which does not involve an image.  by which I mean one using a math problem, or some other  interaction that differs from the letter number things often used.
>> Ideas?
>> Thanks,
>> Karen
Received on Wednesday, 1 February 2017 00:59:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 1 February 2017 00:59:18 UTC