@tibor.pacalat this can be a show stopper especially for governments using Limesurvey because it fully breaks screen reader support and make surveys absolutely inaccessible for handicapped people.
Are there any plans to replace the ugly and not accessible Captchas by a different library?
@DeniChenu, how do you deal with this as Skelvanilla?

@Mazi thank you for notifying me about this. However, I am not aware of any plans to replace the Captchas by a different library.
There is definitely some work to be done to improve accessibility, but we need to set time and man power to do it. I will assign this ticket to me and let you know how are the things standing, when I collect more information.

Fr gouv need/want to put this : https://api.gouv.fr/les-api/api-captchetat

Maybe it's quick for me to create plugin event for Captcha (Can always create some workaround with replacing twig file and controller/action)
@tibor.pacalat : if i create a PR the event : OK to get in stable version and not in dev ?

I think there are 2 steps :

1. Create 2 events (maybe 3):
   • captchaView (twig + js)
   • Validate captcha answer
2. Move core current captcha to plugin core

Captcha in general is a wrong choice for accessibility and inclusion. Public Sector websites must be accessible mandatory.
hCaptcha is not a free software but paid service, although served free (as a beer) also. So, it's a bad choice too.

I suggest to use mCaptcha https://mcaptcha.org/ because it's free (as a bird) software. More, it serve "proof of work" security level. But stills providing dependency on 3rd party software (you still need to install on premise, or use online service)

The better modern choice is to implement a "proof of work" system https://github.com/topics/proof-of-work?l=javascript with no user interaction, inside the core and get rid of un usable unreadable old captcha system.
I think ALTCHA is a good choice https://github.com/altcha-org/altcha the problem it's working on frontend frameworks, not obsolete jQuery.

@tassoman : i still think best is to implement Plugin event for Captcha management :) Default activated can be mcaptcha :)

@DenisChenu thank you for your reply. I suppose I didn't fully get your proposal. I guess you mean to expose ability to hook custom javascript code to twig functions connected to backend.
Maybe is enough code implementation for allowing theme developers to use their own captcha or spam validation system.
I'm still in favour of "proof of work" feature as core element since implementation.

Hey @DenisChenu!
The best choice would be to make the captcha plug-able, so anyone can implement their favourite method of captcha, even select a different captcha type per survey.

Tasks:

• Move existing captcha functionality to a plugin. A new plugin of type 'Captcha'
• Ability to select a default Captcha plugin in global settings
• Allow the user to select the captcha plugin per survey - however captcha settings are only configurable inside the particular captcha plugin

Goal is that any coder should be able to create captcha plugin, if they don't the default captcha plugin.

The default can stay what we currently have.

Allow the user to select the captcha plugin per survey - however captcha settings are only configurable inside the particular captcha plugin

Really need this part ?

This info was from chat with Carsten, so I would say yes.