Closed (works as designed)
Project:
CAPTCHA Pack
Version:
5.x-1.1
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Apr 2009 at 03:28 UTC
Updated:
7 Aug 2012 at 07:54 UTC
Comments
Comment #1
soxofaan commentedIt depends on the target audience you have in mind.
If you really are worried about efficiency and accessibility, you should also try out the Mollom module
Comment #2
mgiffordLots of outstanding issues with the Mollom module unfortunately. Had some complaints lately about it on the Drupal Groups.
So, let's say that we're targeting CAPTCHA configs that need to work for screen readers. Is there any way to configure the existing tools in this set of modules to block bots, but not screen readers?
Mike
Comment #3
soxofaan commentedThe math CAPTCHA (from CAPTCHA pack or CAPTCHA core module), the unrelated word CAPTCHA and maybe even the lost character CAPTCHA should be accessible for screen readers.
How effective these are depends on the sophistication of the spam bots.
But to have a simple baseline performance measure:
say the bots know the set of possible answers (which is rather limited in case of the aforementioned modules) and just pick randomly, the block efficiency would be (with the default settings):
You can configure the challenges to have higher efficiencies.
More sophisticated bots could do better of course, the challenges are not impossible to automate, but I didn't hear of this happening, yet. I even think that the typical spam bots that target low profile sites for the moment are simpler than the random answering scheme described above.
But you shouldn't put these CAPTCHAs on a high profile site of course, it doesn't require a PhD in computer science to write a spam bot that can crack them :)
Comment #4
mgiffordThanks for this! Putting these 3 on random would certainly help confuse the bots. But yes, it's a matter of odds to get rid of all of them.
Oh yeah, could this be put into the documentation for CAPTCHA? That way it could be available more easily for others.
Mike
Comment #5
tinker commentedSeems to be answered. 5.x issues no longer supported.