You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had a complaint from someone unable to joint the Social Incubator CG because they can't/won't run the code for the mandatory Google reCAPTCHA. I expect to see more such complaints from members of free software and decentralisation communities; in general many find it disheartening that the first hurdle to getting involved with projects that align with their values in W3C is to jump through hoops that don't. Ethically I agree with their concerns, but pragmatically I understand there are limited resources to deal with problems like this. I know we can't fix it overnight, and indeed that many people won't see an problem at all really.
I'm opening this issue though so we can track it in case there are resources to explore alternatives. Please let me know if this isn't the right place and there's somewhere more appropriate to take it to.
there is unfortunately no alternative to reCAPTCHA today in our account creation path
the W3C account creation workflow is being revamped as part of the site design (planned to be released in June), and the suggestion to provide paths that don't include captchas was added to the list of requirements that will be considered
Since the issue you raise apply pretty specifically to reCAPTCHA itself (rather than captchas in general), I wonder if you or the Social Incubator CG community knows of robust alternatives that we could consider in the shorter term? We're aware of hCaptcha but at least when our team evaluated it a few months ago, it didn't seem to have the level of usability/accessibility we needed.
I've had a complaint from someone unable to joint the Social Incubator CG because they can't/won't run the code for the mandatory Google reCAPTCHA. I expect to see more such complaints from members of free software and decentralisation communities; in general many find it disheartening that the first hurdle to getting involved with projects that align with their values in W3C is to jump through hoops that don't. Ethically I agree with their concerns, but pragmatically I understand there are limited resources to deal with problems like this. I know we can't fix it overnight, and indeed that many people won't see an problem at all really.
I'm opening this issue though so we can track it in case there are resources to explore alternatives. Please let me know if this isn't the right place and there's somewhere more appropriate to take it to.
See also: CAPTCHAs are horrible TAG issue.
The text was updated successfully, but these errors were encountered: