W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > December 2014

RE: Google Can Now Tell You're Not a Robot With Just One Click

From: Milliken, Neil <neil.milliken@atos.net>
Date: Tue, 9 Dec 2014 10:50:28 +0000
To: Elle <nethermind@gmail.com>, Steve Lee <steve@opendirective.com>
CC: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, John Rochford <john.rochford@umassmed.edu>
Message-ID: <81F26D57E7177840AC55370BD1846A782C5BD702@DEERLM99EZ3MSX.ww931.my-it-solutions.net>
Agree with Elle that the intention here is good and that we should be encouraging  and praising improvements even if they are small.

Kind regards,

Neil Milliken
Head of Accessibility & Digital Inclusion
M: +44 781 232 5386
T: +44 203 618 0957
E: Neil.Milliken@atos.net<mailto:Neil.Milliken@atos.net>


From: Elle [mailto:nethermind@gmail.com]
Sent: Monday, December 08, 2014 2:41 PM
To: Steve Lee
Cc: public-cognitive-a11y-tf; John Rochford
Subject: Re: Google Can Now Tell You're Not a Robot With Just One Click

Hi, Steve:

We've just begun our testing, but we have found that in an authenticated state (i.e. logged into Google apps, cached indicators of identity, etc.), both VoiceOver/Safari and NVDA/Firefox worked well. Additionally, Dragon NaturallySpeaking (14) worked well. We're doing testing on mobile, JAWS, and several unauthenticated scenarios this week, and we're setting up some user testing to get real-world feedback.

I think that there are two things that are getting confusing in the public forums (Twitter, WebAIM, etc.): people seem to maintain that to like this solution one must like and approve of CAPTCHA, and people express frustration and anger at the inaccessible state of the fallback.  Here's our position on both.

  1.  CAPTCHA is still a faulty concept. When we talk about early signs of accessibility improvements, we aren't saying that this CAPTCHA solution provides good for security or that it cannot be hacked. Frankly, that's not our concern. We still believe that CAPTCHA is not ideal, since it does put a technical problem upon the user to solve, and it's a mousetrap that's bound to fail if the cheese is enticing enough.
  2.  Intentional improvement, even if not 100%, is still worth praising. When we look at scenarios that seem to require the CAPTCHA fallback, it's not an improvement, but it's also not any different than it was before Google's no-CAPTCHA was released. I humbly maintain that while inaccessible solutions should not be tolerated, Google seems to be incurring wrath from even attempting to include any accessibility improvements in their most recent implementation. Maybe that's why they didn't even mention it in their blog posts - what a missed opportunity to educate others about inclusive design. I would rather encourage them to keep working at this on the unauthenticated state until a better idea comes along.

Again, I'd really appreciate anyone's feedback if they've tested this. When our next round of testing is complete, we'll publish those results on our site (www.simplyaccessible.com<http://www.simplyaccessible.com>).

All the best,

If you want to build a ship, don't drum up the people to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea.
- Antoine De Saint-Exupéry, The Little Prince

On Sat, Dec 6, 2014 at 4:16 PM, Steve Lee <steve@opendirective.com<mailto:steve@opendirective.com>> wrote:


Thanks, that is positive. Any thing that gets us closer to forcing bots to prove they are human rather than us proving we are not bots is good.

What's not clear from that post is if the non mouse interactions ever worked or if they always required the captcha fallback. I assume the latter.

What of mobile use which only has touch events? Again I assume fallback only.


Autocomplete may have messed with my text
On 6 Dec 2014 02:04, "Elle" <nethermind@gmail.com<mailto:nethermind@gmail.com>> wrote:


We're doing a lot more testing (technical and with real users), but our first round has been promising: http://simplyaccessible.com/article/googles-no-captcha/

We'd also like to test this implementation with those who have struggled with other CAPTCHA challenges from a cognitive perspective. If anyone has suggestions on this, please share!

Much appreciated,
On Dec 4, 2014 7:14 AM, "Rochford, John" <john.rochford@umassmed.edu<mailto:john.rochford@umassmed.edu>> wrote:
Hi All,

Google Can Now Tell You’re Not a Robot With Just One Click

This seems promising.


John Rochford
UMass Medical School/E.K. Shriver Center
Director, INDEX Program
Instructor, Family Medicine & Community Health
Twitter: @ClearHelper

Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.
Received on Tuesday, 9 December 2014 11:03:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:23 UTC