1. We can implement most of these in Evergreen.
2. We don't need to ask the system administrators to subscribe to a third party CAPTCHA product.
3. Most of these provide accessibility solutions, though not foolproof.
I think that if we employ two or three of these things on this page, we will see a dramatic drop in spam submissions!
Reading that makes me want to code something right away!
PS. I was considering a "roll your own" CAPTCHA. Like this example:
<label for="cap">Please type the name of the library for which you are registering. The exact spelling is shown to you in the dropdown menu above</label>
<input name="cap" type="text" />
Jane - that article captivated me for more than a half hour! Wow! I am left with no solution. It seems that it's a catch 22.
But I love the ideas presented here: https:/ /webaim. org/blog/ spam_free_ accessible_ forms/
For three reasons:
1. We can implement most of these in Evergreen.
2. We don't need to ask the system administrators to subscribe to a third party CAPTCHA product.
3. Most of these provide accessibility solutions, though not foolproof.
I think that if we employ two or three of these things on this page, we will see a dramatic drop in spam submissions!
Reading that makes me want to code something right away!
PS. I was considering a "roll your own" CAPTCHA. Like this example:
<label for="cap">Please type the name of the library for which you are registering. The exact spelling is shown to you in the dropdown menu above</label>
<input name="cap" type="text" />