W3C home > Mailing lists > Public > public-rqtf@w3.org > June 2019

CAPTCHA Update--An extended opportunity

From: Janina Sajka <janina@rednote.net>
Date: Mon, 3 Jun 2019 13:08:31 -0400
To: public-rqtf@w3.org, public-cognitive-a11y-tf@w3.org, apa Lisa Seeman <lisa.seeman@zoho.com>, "White, Jason J" <jjwhite@ets.org>, jennie.wai@rednote.net
Message-ID: <20190603170831.GC2843@rednote.net>
Colleagues:

While APA's recent Call for Consensus agreed on publishing a second wide
review CAPTCHA draft, we were unable to announce our publication widely
as we had expected to do. This is because the announcement of a new
agreement between W3C and WHAT was published at the same time we
intended to post our review request. We did not want to compete, or
overshadow the important development with HTML.

Consequently, we are pushing back the formal announcement and
publication of our second wide review CAPTCHA draft until next week.
This provides an extended opportunity for comments, but also an extended
opportunity to affect the draft that will be the second wide review
publication itself.

Here's the new schedule as it now stands:

1.)	Edits to the Editor's Draft for inclusion in the wide review
publication will be accepted through 23:59 (Midnight) Boston Time this
coming Sunday 7 June.

2.)	A brief CfC to publish will be conducted by APA next week as
there are already substantive edits proposed for the Editor's Draft on
github.

3.)	The second wide review publication, together with blog posts and
other announcements are now scheduled for Friday 14 June.

4.)	The public comment period will run through 23:59 (Midnight)
Boston Time on Sunday 14 July.

***	Considerations  to Bear in Mind ***

Please note several editorial corrections are already present in the
Editor's Draft, and others are queued for addition as I write this
message:

https://w3c.github.io/apa/captcha/

One suggestion from the COGA Task Force, which I believe came from
Jennie Delisi, is now used in Sec. 1.2 of the Editor's Draft here:

http://www.w3.org/TR/turingtest/#the-accessibility-challenge

Specifically, we now cite "auditory processing disorders" as an example,
and I believe this enhances the document in several ways including by
providing a more parallel syntactic sentence structure in that
introductory paragraph.

Further suggestions are most welcome. However, please note this document
does not discuss disabilities per se. Rather, it discusses functional
impediments faced by people with disabilities in specific CAPTCHA
approaches. Therefore, we're most interested in hearing of any
functional impediments not currently covered for specific CAPTCHA
approaches. We are also particularly interested in any CAPTCHA
approaches we may have not discussed.

Best,

Janina


-- 

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 Monday, 3 June 2019 17:08:59 UTC

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