WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: reCAPTCHA replacement


From: Jonathan Avila
Date: Jun 30, 2015 11:57AM

We have seen the same issues with reCAPTCHA on iOS. I wonder if the link below is a good place to file the bug report


Jonathan Avila
Chief Accessibility Officer

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Paul J. Adam
Sent: Tuesday, June 30, 2015 11:12 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] reCAPTCHA replacement

Bug #
Steps to Reproduce
Expected Results
Actual Results
User Agent
Assistive Technology
URL to Bug Report
Bug Report ID#
Bug Reported By
Additional Notes
Bug Tracker
Details/Bug Reporting Guidelines
Bug Type
Google reCAPTCHA api2 not accessible to VoiceOver iOS users.
After activating the I'm not a robot checkbox the verification challenge opens but the iOS VO focus is still on the checkbox and they do not get focus shifted to the actual challenge widget. Even though there is an announcement "Opening verification challenge" when the VO user swipes to the next elements their focus never goes into the challenge window. If a user were to get lucky with expore by touch navigation and open the audio challenge then they would find that the text input to enter the challenge answer has no accessible name. The image based challenges for finding pictures of cake or other items are not accessible to the screen reader due to lack of alt text. The audio challenge is difficult to impossible to complete in the allotted amount of time due to short challenge expiration window. The garbled audio challenges that sound like paranormal activity are basically impossible to complete.
1. Open https://www.google.com/recaptcha/api2/demo in Mobile Safari on iOS 2. Turn on VoiceOver 3. Activate I'm not a robot checkbox Focus shifts into the challenge widget as expected. User can then swipe to the audio challenge button. User is able to type the audio challenge into the answer text box which has an accessible name before their time expires.
Focus remains on the I'm not a robot checkbox. User cannot swipe into the challenge widget. User cannot activate audio challenge button. Audio challenge answer text input has no accessible name. User cannot type audio challenge answer in time before it expires and they have to start over again.

iOS 8.3
Mobile Safari
Not Fixed
Paul J. Adam
Filed under Google's get in touch accessibility contact form not sure where to file this?

reCAPTCHA api2 Accessibility Docs:
Chromium bug tracker

Did I file this bug report in the right location? http://www.google.com/accessibility/get-in-touch.html <http://www.google.com/accessibility/get-in-touch.html>; It's not really a bug tracker. Should bugs for it go in the Android or Chrome bug trackers?

Paul J. Adam
Accessibility Evangelist

Join us at our Mobile Accessibility "Bootcamp!"
August 6-7 in Austin Texas
Topics include responsive web design, native apps, & more

> On Jun 30, 2015, at 9:53 AM, Nancy Johnson < <EMAIL REMOVED> > wrote:
> ReCaptcha update? . Does Google intend to fix the issues?
> Recommendations? What is the mobile experience with the images?
> I just tried Patrick's sample on my desktoup. After refreshing maybe
> twice, the the mobile version verification displayed.
> The images were totally inaccessible using tab key, arrows and space
> bar. The focus went to the icons at the bottom of the page.
> When I selected the headphones and listened with NVDA, the
> background noise was so bad I could not hear the numbers using
> different browsers trying several times. I was never able to hear the
> correct numbers.
> I have a mid-range hearing loss, with hearing aids and some issues
> with digital but wouldn't call it severe.
> This version is a big draw because it eliminates the numbers..
> Thanks Nancy
> On Fri, Dec 5, 2014 at 10:50 PM, Randy Pope < <EMAIL REMOVED> > wrote:
>> Speaking as a deaf-blind person, both legally blind with little sight
>> and deaf, I just did a quick review of Google new replacement.
>> Firefox: When I first click on the link, I got this checkbox message
>> asking me if I'm not a robot. I click that and it appears I got
>> through. No graphic photo or CAPTCHA to deal with. That's good. Five
>> minutes later I again test the site but this time the old reCAPTCHA
>> appeared on the screen which required me to type in the information
>> on the image. Since I cannot see the screen well enough, I was
>> unable to type in the information, I'm also deaf which may the audio challenge completely useless for me.
>> IE 11: I follow the same steps as I did with Firefox and got the same
>> result. I have tried closing IE and click on the same link at
>> different time, ten minute apart and still got the same result.
>> To me this Google new replacement remains to be inaccessible for the
>> people who are deaf-blind. Thank you, Alastair, for sharing this
>> link. This information has re-generated my energy and reinforce my
>> belief against CAPTCHA in any form.
>> Randy Pope
>> -----Original Message-----
>> [mailto: <EMAIL REMOVED> ] On Behalf Of Alastair
>> Campbell
>> Sent: Thursday, December 04, 2014 9:11 AM
>> To: WebAIM Discussion List
>> Subject: [WebAIM] reCAPTCHA replacement
>> Interesting post from Google on their update/replacement for re-CAPTCHA:
>> http://googlewebmastercentral.blogspot.co.uk/2014/12/are-you-robot-in
>> troduci
>> ng-no-captcha.html
>> The short story is that they are replacing the current CAPTCHA method
>> (distorted image-text or distorted audio) with a simple tickbox for
>> "I am not a robot". They then use some heuristics based on IP
>> address, browser config, mouse pointer behaviour etc. to guess if you are a robot.
>> That bit about using mouse movements to analyse your human-ness
>> obviously rang alarm bells, and I couldn't find an example easily, so
>> I created one
>> here:
>> https://alastairc.ac/testing/recaptcha-test.html
>> At first glance, it is keyboard accessible, has appropriate ARIA
>> attributes (which are needed as they use a span for a checkbox), and
>> it didn't fail when I only used the keyboard.
>> Overall, it looks like an important improvement from an accessibility
>> point of view. If the heuristics fail you then you get the
>> traditional CAPTCHA approach, however, that should be a lot less frequent.
>> It would be interesting to see how the image-matching version works
>> from an accessibility point of view, I didn't find a way to trigger
>> that within my lunch break.
>> -Alastair
>> PS. Alt text for the images in the blog post:
>> 1. A traditional CAPTCHA where you have to type in the distorted
>> words shown, or choose the audio option.
>> 2. An animated image showing a checkbox with label "I'm not a robot",
>> and the reCAPTCHA logo.
>> 3. The checkbox shows the traditional method underneath.
>> 4 & 5. Two examples of the checkbox showing an image of a cat, and
>> then nine images underneath that to match against.
>> >> >> list messages to <EMAIL REMOVED>
>> >> >> list messages to <EMAIL REMOVED>
> > > archives at http://webaim.org/discussion/archives