Skip to content

Correct missing ReCAPTCHA version numbers. Closes #17. #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 2, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -253,15 +253,15 @@

Version 2: Are you a robot?

The Non-interactive Version 3


Late in 2018 Google released reCAPTCHA v3 promising to eliminate "the need to interrupt users with challenges at all." Google also informed us that their goals with v included increasing "the accessibility of the web by removing traditional CAPTCHAs" entirely. Obviously, fully non-interactive Turing testing is a most welcome development direction for accessibility. When the non-interactive Turing test 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.

Late in 2018 Google released reCAPTCHA v3 promising to eliminate "the need to interrupt users with challenges at all." Google also informed us that their goals with v3 included increasing "the accessibility of the web by removing traditional CAPTCHAs" entirely. Obviously, fully non-interactive Turing testing is a most welcome development direction for accessibility. When the non-interactive Turing test 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.


Of course no approach will always return unambiguous results.

href="https://developers.google.com/recaptcha/docs/v3">In such
situations Google advises 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 reCAPTCHA v2 Invisible service.

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 reCAPTCHA v2 Invisible service.


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 Turing testing. Sadly this leaves the door open to any fallback approach a content provider might choose. Meanwhile, Google's reCAPTCHA FAQ declares that reCAPTCHA Version 2 is not going away. 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.


Expand Down