Last modified: 2013-04-27 00:29:17 UTC
"Load a new one" can be worded however you see fit, but I'm thinking that if we do this then we may avoid people who instantly see a captcha and look for an alternative (sending more work to ACC). When they've failed to complete the captcha correctly for the first time *then* can we show them the link to Request an account (perhaps making it even more prominent?)
If we do this, we should make sure it still links to "Request an account" if they don't have JavaScript (which is required for the refresh button).
(In reply to comment #0) > "Load a new one" can be worded however you see fit, but I'm thinking that if > we > do this then we may avoid people who instantly see a captcha and look for an > alternative (sending more work to ACC). > > When they've failed to complete the captcha correctly for the first time > *then* > can we show them the link to Request an account (perhaps making it even more > prominent?) This is a clever idea, but I don't think we can do it. The request an account function is primarily aimed at the blind and others who will never be able to fill out the CAPTCHA even with refresh, and hiding or obscuring the request function on first view is likely to make things even worse from an accessibility standpoint. The account request call to action is already below the refresh and input field to try and get people to try refresh first.
Actually, reopening instead of wontfixing. We won't tackle this right away, but if we ever add proper accessibility support (like an audio CAPTCHA) it could happen.
