CAPTCHA systems are there to differentiate between automated bots and real users. Unfortunately, as you've noted, they aren't very convenient (in particular for disabled users).

Whether it's "a good idea" or not depends on your use case, really, although they aren't very efficient with user logins: they are not very useful to prevent password guessing attacks and implementing a rate limiter in the application is more convenient to the user while implementing a TOTP PIN provides better security.

Having some form of "proof of work" from your client might still be a very good idea if you're going to spend server resources for them and if these resources are limited. A typical use case for such query are system that will perform work for anonymous users (for instance, a web-based WHOIS application could use that to preserve resources).

CAPTCHA systems are there to differentiate between automated bots and real users. Unfortunately, as you've noted, they aren't very convenient (in particular for disabled users).

Whether it's "a good idea" or not depends on your use case, really, although they aren't very efficient with user logins: they are not very useful to prevent password guessing attacks and implementing a rate limiter in the application is more convenient to the user while implementing a TOTP PIN provides better security.

Having some form of "proof of work" from your client might still be a very good idea if you're going to spend server resources for them and if these resources are limited. A typical use case for such query are system that will perform work for anonymous users (for instance, a web-based WHOIS application could use that to preserve resources).