Merge pull request #18 from w3c/editorial

jasonjgw · github-actions[bot] · jasonjgw · commit bd0b902c1a76 · 2022-02-02T19:39:58.000Z
SHA: 8e625da Reason: push, by @jasonjgw Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
diff --git a/index.html b/index.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html><html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
 <meta charset="utf-8">
-<meta name="generator" content="ReSpec 29.0.1">
+<meta name="generator" content="ReSpec 29.0.4">
 <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
 <style>
 dfn{cursor:pointer}
@@ -590,15 +590,15 @@
       "title": "Accessibility requirements for ICT products and services"
     }
   },
-  "publishISODate": "2022-01-31T00:00:00.000Z",
-  "generatedSubtitle": "Editor's Draft 31 January 2022"
+  "publishISODate": "2022-02-02T00:00:00.000Z",
+  "generatedSubtitle": "Editor's Draft 02 February 2022"
 }</script>
 <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
 	<body class="h-entry informative"><div class="head">
     <a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72">
   </a> <h1 id="title" class="title">Inaccessibility of CAPTCHA</h1>
     <h2 id="subtitle" class="subtitle">Alternatives to Visual Turing Tests on the Web</h2>
-    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2022-01-31">31 January 2022</time></p>
+    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2022-02-02">02 February 2022</time></p>
     <details open="">
       <summary>More details about this document</summary>
       <dl>
@@ -929,14 +929,14 @@ <h2 id="subtitle" class="subtitle">Alternatives to Visual Turing Tests on the We
 			<section id="recap3"><h4 id="x3-2-2-the-non-interactive-version-3"><bdi class="secno">3.2.2 </bdi>The Non-interactive Version 3</h4><a class="self-link" href="#recap3" aria-label="Permalink for Section 3.2.2"></a>
 			
 
-<p>Late in 2018 Google released <a href="https://webmasters.googleblog.com/2018/10/introducing-recaptcha-v3-new-way-to.html"> reCAPTCHA v3</a> promising to eliminate "the need to interrupt users with challenges at all." <a href="https://lists.w3.org/Archives/Public/public-rqtf/2019Mar/0019.html">Google also informed us</a> that their goals with v included increasing "the accessibility of the web by removing traditional CAPTCHAs" entirely. Obviously, fully non-interactive <a href="#dfn-turing-test" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-turing-test-4">Turing testing</a> is a most welcome development direction for accessibility. When the non-interactive <a href="#dfn-turing-test" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-turing-test-5">Turing test</a> returns a score indicating high confidence that the user is human, or indeed a score indicating high confidence that the user is a robot, and experience has demonstrated the non-interactive engine is reliable, we can only offer praise and gratitude for technological progress that more effectively supports persons with disabilities. </p>
+<p>Late in 2018 Google released <a href="https://webmasters.googleblog.com/2018/10/introducing-recaptcha-v3-new-way-to.html"> reCAPTCHA v3</a> promising to eliminate "the need to interrupt users with challenges at all." <a href="https://lists.w3.org/Archives/Public/public-rqtf/2019Mar/0019.html">Google also informed us</a> that their goals with v3 included increasing "the accessibility of the web by removing traditional CAPTCHAs" entirely. Obviously, fully non-interactive <a href="#dfn-turing-test" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-turing-test-4">Turing testing</a> is a most welcome development direction for accessibility. When the non-interactive <a href="#dfn-turing-test" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-turing-test-5">Turing test</a> returns a score indicating high confidence that the user is human, or indeed a score indicating high confidence that the user is a robot, and experience has demonstrated the non-interactive engine is reliable, we can only offer praise and gratitude for technological progress that more effectively supports persons with disabilities. </p>
 
 <p>Of course no approach will always return unambiguous results. <a href="https://developers.google.com/recaptcha/docs/v3">In such
 	situations Google advises</a>  that content providers "use a secondary
 challenge that makes sense in the context of their site such as two-factor
 authentication, send the post to moderators, or combine the score with signals
 specific to their site to make a more informed judgment." Google intends
-that traditional CAPTCHA no longer be used as a  fallback mechanism and has dropped  it from v reCAPTCHA, though it remains in their slightly older, 2017 <a href="https://developers.google.com/recaptcha/docs/invisible">reCAPTCHA v2 Invisible</a> service.</p>
+that traditional CAPTCHA no longer be used as a  fallback mechanism and has dropped  it from v3 reCAPTCHA, though it remains in their slightly older, 2017 <a href="https://developers.google.com/recaptcha/docs/invisible">reCAPTCHA v2 Invisible</a> service.</p>
 
 <p>The reality is that what action is taken in response to an ambiguous core returned by v3 is in the hands of the content provider. Services like reCAPTCHA gain their market share by offering to relieve the content provider of the hard work inherent in mounting effective and accessible <a href="#dfn-turing-test" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-turing-test-6">Turing testing</a>. Sadly this leaves the door open to any fallback approach a content provider might choose. Meanwhile, Google's reCAPTCHA FAQ declares that <a href="https://developers.google.cn/recaptcha/docs/faq">reCAPTCHA Version 2 is not going away</a>. It is therefore imperative that methods for disambiguating an ambiguous non-interactive score be well documented and easily implementable in order to better overcome the tendency to simply adopt the old familiar approach. </p>
 
