Change Details

## Summary Currently, we immediately execute hCaptcha as soon as the user interacts with the account creation form. This reduces submission delay but may interrupt the signup flow by potentially showing an intrusive challenge. We would instead like to defer executing hCaptcha until the user submits the form. ## Acceptance criteria - [ ] hCaptcha challenge does not display until user presses the submit button - [ ] hCaptcha JS loads on first form interaction

## Summary Currently, we immediately execute hCaptcha as soon as the user interacts with the account creation form. This reduces submission delay but may interrupt the signup flow by potentially showing an intrusive challenge. We would instead like to defer executing hCaptcha until the user submits the form. ## Acceptance criteria - [x] hCaptcha challenge does not display until user presses the submit button - [x] hCaptcha JS loads on first form interaction

## Summary Currently, we immediately execute hCaptcha as soon as the user interacts with the account creation form. This reduces submission delay but may interrupt the signup flow by potentially showing an intrusive challenge. We would instead like to defer executing hCaptcha until the user submits the form. ## Acceptance criteria - [ - [x] hCaptcha challenge does not display until user presses the submit button - [ - [x] hCaptcha JS loads on first form interaction