Just published a blog post tearing into hCaptcha’s so-called “accessibility” mode.
It’s not accessibility. It’s a cookie. And to get that cookie, you now have to submit your email and send a code via SMS to an U.S. phone number. It fails silently. It doesn’t confirm anything. You click “Confirm Code” and get “An error has occurred.” No cookie. No fallback. No support. And if you somehow get it? It’s a third-party cookie your browser probably blocks, and it expires. Then you get to do it all again.
Meanwhile, hCaptcha’s text-based challenge — the only mode that might actually work with a screen reader — isn’t tied to the cookie at all. It only shows up if the website owner specifically enables it. Most don’t. So even if you’re blind, even if you’re using assistive tech, you get the same unusable image grid as everyone else.
This isn’t accessibility. It’s exclusion wrapped in PR.
The blog post breaks it all down: how the cookie flow works (or doesn’t), why the system is broken by design, how developers got misled, and what real alternatives look like. If you care about accessible design or just want to understand how bad this gets, read it.
Link: https://fireborn.mataroa.blog/blog/hellcaptcha-accessibility-theater-at-its-worst/
Just released DNS-tester — is a scalable tool designed for enterprise environments to validate DNS cache consistency, monitor performance across distributed DNS infrastructure, and ensure reliable name resolution at scale.! Perfect for sysadmins and devs. 
Save the date!
Live technical Q&A
Real-world use cases
Introducing **Chakra** - a blazing fast in-browser WebAssembly runtime for builders.
Read more: 
