1. I've just come across a website that I had to check with #Aira, because there was an inaccessible #captcha on it.
2. Bypassing the captcha by clicking 'next' *looks* like it would be valid and you can fill out content on future pages, but when you get to the end, you're told to: 'Correct the errors highlighted.'
Not much help to a #ScreenReader user.
3. Terms and conditions are on-click, not bogstandard checkboxes, so you're not always sure whether it's checked or not checked.
4. The country select was not a standard combo/list box, but a weird spin control that didn't at all play nicely.

It's one of those days and it isn't even Thursday...

Please, please do not do this under any circumstance, if you care about your instance being accessible to the #blind and visually impaired (hint, you should).

#HCaptcha is a horrible example of how not to implement a #captcha solution, forcing people to register their email address and store a cookie, as well as disable cross origin restrictions on their devices in order to pass validation.

There are much better alternatives, such as the no-hassle https://github.com/mCaptcha/mCaptcha, which does not need any user input other than checking a checkbox. Alternatively, use captchas that provide text versions, e.g. via solving a math question or at the very minimum, provide an audio version, knowing that it is not ideal for the hearing impaired.

HCaptcha is NOT the future. #accessibility #a11y

GitHub - mCaptcha/mCaptcha: A no-nonsense CAPTCHA system with seamless UX | Backend component

A no-nonsense CAPTCHA system with seamless UX | Backend component - GitHub - mCaptcha/mCaptcha: A no-nonsense CAPTCHA system with seamless UX | Backend component

^GitHub