W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2004

[whatwg] Bot protection

From: Matthew Thomas <mpt@myrealbox.com>
Date: Tue, 28 Dec 2004 16:03:12 +1300
Message-ID: <02E93090-587D-11D9-8D70-000A95AD3972@myrealbox.com>
On 28 Dec, 2004, at 1:51 PM, Robert Accettura wrote:
> ...
> <captcha type="multi">
>  <option method="img" type="text"/>
>  <option method="audio" type="text"/>
>  <option method="esp" type="text"/>
> </captcha>
>
> In the above, the UA would realize human interaction is needed.  It 
> has been given a choice of 3 options and enter text based upon them.  
> This way a visually impared person can choose to never use an img.  
> And a deaf person can choose never to use audio.
> ...

What does this do that HTTP's Accept: header doesn't already do? If you 
have a sight impairment, your screenreader can (and should) tell 
servers that you prefer audio to graphics, so you can be served audio 
captchas instead of graphical ones.

Alternatively, you could use nested HTML <object>s for this (provided 
that the text, image, and audio tests had the same answer, since the 
server couldn't tell which one was being used). <object> isn't yet 
implemented properly in released versions of Safari, or Internet 
Explorer for Windows, but it's still implemented in more browsers than 
any element that hasn't been invented yet.

-- 
Matthew Thomas
http://mpt.net.nz/
Received on Monday, 27 December 2004 19:03:12 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:38 UTC