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

RE: Finalizing CAPTCHA

From: Scott Hollier <scott@hollier.info>
Date: Mon, 29 Jul 2019 23:51:49 +0000
To: Janina Sajka <janina@rednote.net>, "public-rqtf@w3.org" <public-rqtf@w3.org>
Message-ID: <SN6PR01MB4349A06F98BF479B92BCA7F5DCDD0@SN6PR01MB4349.prod.exchangelabs.com>
To Janina

Just reviewed the changes - all looks great to me. Great work on this. 


Dr Scott Hollier 
Digital Access Specialist 
Mobile: +61 (0)430 351 909
Web: www.hollier.info
Technology for everyone
Australian Access Awards 2019 Call For Nominations - celebrate best practice by nominating your favourite accessible Australian website or app. It's free!  
Keep up with digital access news by following @scotthollier on Twitter and subscribing to Scott's newsletter. 

-----Original Message-----
From: Janina Sajka <janina@rednote.net> 
Sent: Tuesday, 30 July 2019 5:32 AM
To: public-rqtf@w3.org
Subject: Finalizing CAPTCHA


We had one additional comment via github that resulted in an editorial change--a clarification of wording.

So, if you agree, I think we can formally resolve on Wednesday's call to ask APA to launch a Call for Consensus to close work on this revision and publish the latest Editor's Draft as the revised Note.

Here's a summary of changes since the 2nd public comment review

1.)	The Internationalization Working Group provided us revised
language for one paragraph. To read this change, navigate to Sec. 2.1.2 Sound Output and move up one paragraph to the paragraph that begins
with: "While some sites have begun ..." That's the edited paragraph provided by I18N.

2.)	I dropped four words from the beginning of Sec. 1.2 CAPTCHA
Context. I decided there was no reason to talk about large and small web sites, so this section now begins with the words: "Web sites ..."

3.)	We were challenged that one of newer edits, one of the list
items in our revised Conclusion was unclear. I have edited that list item #2 to now read:

    2. Whenever an interactive CAPTCHA is deemed important for security
    reasons, it is very beneficial to limit and minimize how often users
    are subjected to interactive CAPTCHA challenges. With CAPTCHA less
           interactivity is clearly more accessibility. As noted above,
	   we're encouraged by the development of approaches such as
	   Privacy Pass which, even though it still requires an
	   interactive CAPTCHA challenge at
	          times, it does so much less often.

Comments welcome.




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, 29 July 2019 23:52:16 UTC

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