Articles on protecting a form from bots
Short articles that answer a question asked before the product is known: what to do about contact form spam, what the WCAG ask of a CAPTCHA, how to stop fake newsletter sign-ups, how to switch bot checks. Each is useful without Antisy, and says where a bot check fits in.
Contact form spam: what to do, measure by measure
A contact form is open to the whole Internet, and programs find it. First look at what you receive, then add the measures in order of increasing inconvenience for your real visitors: a form checked on the server, a trap field, a limit on bursts, a careful sort of the content, then a bot check. A puzzle to solve is a last resort, not a first reflex.
Published on .
CAPTCHA accessibility: what the WCAG and the W3C say
A CAPTCHA asks a person to prove they are human, and some cannot: an image to recognise for someone who cannot see it, distorted letters for someone who reads with difficulty. The W3C’s accessibility standard, WCAG 2.2, contains two criteria that concern it; the W3C also recommends asking for as little as possible.
Published on .
Fake newsletter sign-ups: what to do, in what order
When programs sign up addresses to your newsletter in bulk, they are often the addresses of people who asked for nothing: your site sends them a message, and your list fills with addresses that are not those of readers. The answer comes down to three steps: confirm each address before the first mailing, limit the confirmation requests, and refuse the form’s automated submissions before writing to anyone.
Published on .
Replacing reCAPTCHA: what to check before you switch
Switching bot checks is mostly an inventory job: where the service is placed, where your server checks its answer, and what happens when one of the two is missing. Start by deciding whether the change is needed, list your forms, replace the two halves together, test the refusals, then remove the old service. A check that works and whose terms you accept does not need replacing.
Published on .
Webflow form spam: what the platform does about it
Webflow describes, in its help, four methods against form spam: a reCAPTCHA field, bot blocking, spam filtering and a trap field. In the pages read, no setting of a native form has your own server check a submission before Webflow accepts it: for that, you have to send the form to your server, and give up what Webflow does with submissions.
Published on .