zaterdag, juli 21, 2007
New CAPTCHA control
I started to work on the site again. I keep running into problems related to the CAPTCHA control that I'm using. It's the free one from the Codeproject site that I modified. Today I got InvalidCastException errors for the Anthem.NET Editlabel component due to this CaptchaWebControl control. So I finally gave up on it and started for a replacement.
Accidently I also found out what CAPTCHA stands for : Completely Automated Public Turing test to tell Computers and Humans Apart. Take that for an acronym :-) . It is an established way to protect web forms against robots and usually involves people filling in a code from an image.
First replacement control I tried was the one created by Peter Kellner. This Microsoft MVP did a nice job of a highly customizable component, but I did not run into the same errors. But the looks were a bit not-done and especially the component only works with events. There is no method to call for verification. As my CAPTCHA is at the bottom of every beta page to allow people to post comments on how to improve my site, I wanted to call verification only when the button was pressed. So I decided against this component.
So as a first for the about2findout.com project, I'm going to use a cheap commercial component. The LanapSoft BotDetect control is available from 59$ onwards and has some excellent features. Not only can I now choose between 50 different CAPTCHA rendering styles, it is also solving a major issue with CAPTCHA. Up till now every website using CAPTCHA was not compliant with section 508 and other accessibility standards because blind people cannot see the code and are thus unable to use the site. This component adds a button that reads out the code as well. Very cool indeed. So with a little investment I get a code that (so far) does not generate more trouble than it's worth and makes my site better adhere to accessibility standards.
Accidently I also found out what CAPTCHA stands for : Completely Automated Public Turing test to tell Computers and Humans Apart. Take that for an acronym :-) . It is an established way to protect web forms against robots and usually involves people filling in a code from an image.
First replacement control I tried was the one created by Peter Kellner. This Microsoft MVP did a nice job of a highly customizable component, but I did not run into the same errors. But the looks were a bit not-done and especially the component only works with events. There is no method to call for verification. As my CAPTCHA is at the bottom of every beta page to allow people to post comments on how to improve my site, I wanted to call verification only when the button was pressed. So I decided against this component.
So as a first for the about2findout.com project, I'm going to use a cheap commercial component. The LanapSoft BotDetect control is available from 59$ onwards and has some excellent features. Not only can I now choose between 50 different CAPTCHA rendering styles, it is also solving a major issue with CAPTCHA. Up till now every website using CAPTCHA was not compliant with section 508 and other accessibility standards because blind people cannot see the code and are thus unable to use the site. This component adds a button that reads out the code as well. Very cool indeed. So with a little investment I get a code that (so far) does not generate more trouble than it's worth and makes my site better adhere to accessibility standards.
