W3C home > Mailing lists > Public > public-rqtf@w3.org > August 2018

RE: Comments on CAPTCHA draft

From: Scott Hollier <scott@hollier.info>
Date: Wed, 8 Aug 2018 00:11:53 +0000
To: "White, Jason J" <jjwhite@ets.org>, Research Questions Task Force <public-rqtf@w3.org>
Message-ID: <MWHPR01MB27660A942F63D082BE47902ADC260@MWHPR01MB2766.prod.exchangelabs.com>
To the RQTF

I've read through the comments and have the following thoughts on the changes:


  *   Privacy considerations: https://github.com/w3c/apa/issues/7
As discussed in our last call, I think it's good to touch on these but I'm hesitant to make this a core focus. While I think it was important to into more detail on security given the purpose of CAPTCHA, privacy concerns for people with disability extend far beyond CAPTCHA so we'd need to proceed with caution as to how much it is referenced


  *   Movement-related CAPTCHA: https://github.com/w3c/apa/issues/6
I've done some digging in the literature and there seems to be very little on this. Has anyone else come across this in a practical sense? In my view, given there's little literature or practical examples I'm hesitant to include it in a standalone section.


  *   Video game CAPTCHA and multi-device authentication: https://github.com/w3c/apa/issues/4#issuecomment-405441394
In my view these points are already addressed in the current draft.


  *   ReCAPTCHA: https://github.com/w3c/apa/issues/5

  *   ReCAPTCHA again: http://lists.w3.org/Archives/Public/public-apa/2018Jul/0010.html

I agree with the comments and the change of wording discussed last week. Following on from David's comments in the last meeting, I think it may be worth differentiating between the ability to check the checkbox and the successful completion of CAPTCHA. i.e. it seems anecdotally that many AT users can locate the checkbox and activate it which is good, but there's also evidence that even if this is achieved, the reCAPTCHA often still believes the person is a bot and the visual CAPTCHAs that are then presented are impossible for many users. The conclusion therefore would be that while reCAPTCHAs show improvement in the consideration of accessibility, they are still not a viable option.

Scott.


[Scott Hollier logo]Dr Scott Hollier
Digital Access Specialist
Mobile: +61 (0)430 351 909
Web: www.hollier.info<http://www.hollier.info>

Technology for everyone

WCAG 2.1 has arrived - is your organisation ready<http://www.hollier.info/consultancy/>? Keep up-to-date by following @scotthollier on Twitter<https://twitter.com/scotthollier> and subscribing to Scott's digital access newsletter<mailto:newsletter@hollier.info?subject=subscribe>.

From: White, Jason J <jjwhite@ets.org>
Sent: Tuesday, 7 August 2018 3:49 AM
To: Research Questions Task Force <public-rqtf@w3.org>
Subject: Comments on CAPTCHA draft

Dear colleagues,

Listed below are the comments that I could find on the CAPTCHA Note draft. Please add whatever I have missed to this list.
CAPTCHA comments

  *   Privacy considerations: https://github.com/w3c/apa/issues/7
  *   Movement-related CAPTCHA: https://github.com/w3c/apa/issues/6
  *   Video game CAPTCHA and multi-device authentication: https://github.com/w3c/apa/issues/4#issuecomment-405441394
  *   ReCAPTCHA: https://github.com/w3c/apa/issues/5

  *   ReCAPTCHA again: http://lists.w3.org/Archives/Public/public-apa/2018Jul/0010.html



________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

image001.gif
(image/gif attachment: image001.gif)

Received on Wednesday, 8 August 2018 00:12:24 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 January 2023 20:26:45 UTC