This WCAG 2.2 success criterion could be useful in the war against CAPTCHA. https://www.w3.org/TR/WCAG22/#accessible-authentication-minimum #a11y

"I am not a robot" tests are inherently ableist.

Web Content Accessibility Guidelines (WCAG) 2.2

Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on any kind of device (including desktops, laptops, kiosks, and mobile devices). Following these guidelines will also often make web content more usable to users in general.

@heydon Thank you for sharing! New to this, but it's interesting how honeypot form fields are often overlooked as a powerful anti-spam solution. I wonder why, they're simple yet effective! I'm optimistic about the increasing support for passkeys as an accessible and user-friendly alternative, though.
@vicgolding In my last contract, I insisted we added a honeypot where there was only a CAPTCHA. Still had spam with just the CAPTCHA; honeypot got rid of it, and for months. Still no spam as far as I know.