W3C home > Mailing lists > Public > public-wai-announce@w3.org > April to June 2019

Updated "Inaccessibility of CAPTCHA" Draft for Wide Review

From: Janina Sajka <janina@rednote.net>
Date: Wed, 26 Jun 2019 18:12:18 +0000
To: public-wai-announce@w3.org
Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>, public-rqtf@w3.org
Message-ID: <20190626181148.GF11187@rednote.net>
Today the Accessible Platform Architectures (APA)[1] Working Group, with the
assistance of its Research Questions Task Force (RQTF)[2], has published
another draft update to the W3C Note "Inaccessibility of CAPTCHA", first
published in 2005:

http://www.w3.org/TR/turingtest

We thank the community for comments provided on earlier drafts of this
document. Your comments have helped us improve our analysis of the state
of the art in telling human users apart from their robotic
impersonators.

While there are editorial revisions in almost every paragraph of this latest
draft, some of the highlights include:

 * A new section on Proof of Work
   <http://github/w3c/apa/captcha/#proof-of-work;

 * A significant rewrite of the section on reCAPTCHA
   <http://github/w3c/apa/captcha/#the-google-recaptcha>;

 * Two new sections on Turing Tokens
   <http://github/w3c/apa/captcha/#privpass> and Federated Turing
   Tokens <http://github/w3c/apa/captcha/#fedtoken> to discuss recent
   noninteractive blinded verification approaches which we've named
   "Turing Tokens."

To be sure the updated document is as complete as possible, we once again
solicit public input on this version. The following questions will help
guide your review:

 * Does this document fully capture current problems with CAPTCHA and
   related systems?
 * Are there other CAPTCHA approaches that should be added?
 * Are there concerns for certain categories of persons with
   disabilities that remain unaddressed or insufficiently addressed in
   this document?
 * Are you aware of relevant research or technological development in
   this area we missed?
 * Have we sufficiently addressed CAPTCHA's problems with
   internationalization, privacy, and security?
 * Is "Turing Tokens" a reasonable name for the blinded verification
   tokens described in section 3.4? And, is our new visionary section
   3.5 based on Turing Tokens clear? Or, should it be its own, separate
   document?
 * Have we mis-characterized anything we discuss?

To comment, please file an issue in the W3C apa GitHub repository[3]. If this is
not feasible, send email to public-apa@w3.org (comment archive[4]).
Comments are requested by 26 July 2019. In-progress updates to the document
may be viewed in the publicly visible editors' draft[5].

Janina Sajka, Chair
Accessible Platform Architectures (APA) Working Group

[1] http://www.w3.org/wai/apa/
[2] https://www.w3.org/WAI/APA/task-forces/research-questions/
[3] https://github.com/w3c/apa/issues/new
[4] http://lists.w3.org/Archives/Public/public-apa/
[5] https://w3c.github.io/apa/captcha/


-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Thursday, 27 June 2019 02:58:36 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 June 2019 02:58:38 UTC