I tested and seems accessible on the live demo. Not sure if is as protected as the author claims though, but it might throw some bots for a spin.

> but it might throw some bots for a spin.

Until some bot dev sees this, accepts the challenge, and then solves it as a function within their package that never needs updating again because it is now done. So, live it up while it is not solved. After that, just shrug your shoulders at yet another idea no longer being useful

The key in this case is that this is not a problem for me even if someone implements such a protection.

The rest is mice and traps.

Man, I’ve always wondered how to test apps with a (simulated) screen reader, but never got too far

My secret is that I'm not simulating. Being blind forces you into it. :D

For testing purposes, the nvda screen reader is free and open source. I'm not sure if there is a driver for it to have an api access to what it would output, but it might be a fun project to try for a11y testing purposes.

Thank you! And sorry for all the shitty code I produced over the years.

I use this: https://chromewebstore.google.com/detail/aria-devtools/dneem...

Not sure about desktop apps.

Added this. Thank you a lot!

Given the entire bottom section, it seems like accessibility was taken into account here.

Unfortunately then I think it won't help at all - going through the accessibility tree is a standard web crawling play.