Editing CAPTCHA (section)

==Alternatives==
The W3C also outlined potential consumer-positive alternatives to CAPTCHAs:<ref>{{Cite web |title=Captcha Alternatives and thoughts |url=https://www.w3.org/WAI/GL/wiki/Captcha_Alternatives_and_thoughts |website=W3C wiki}}</ref>

#Honeypot - "Another method to detect automated submissions. The idea behind the honeypot method is as follows: website forms would include a hidden field (by positioning the field off screen). Since spam robots cannot detect a hidden field in the HTML, when data is inserted into this 'honeypot' field, the website administrator would know that the data was not entered by a 'real' user."
#Temporary tokens - after a user passes a CAPTCHA, a token is accepted onto the user's device allowing them to use the associated webservice for a fixed amount of time.
#Multi-factor authentication - using a pre-arranged secondary device to independently authenticate identity.
#Biometric security - facial recognition, fingerprint, retinal scan. This would only be acceptable in an institution with very high security requirements.

<blockquote>"Users should not be forced beyond what is strictly necessary to keep a site secure, e.g.,/ if a honeypot suffices, use a honeypot until evidence of robotic attacks dictates something else." - W3C<ref name=":1" /></blockquote>