Sign-Up Button Remains Enabled Despite Invalid or Empty Password Input

[mani6409]

Problem

The sign-up form does not appear to enforce the displayed password requirements before allowing users to proceed. The password field accepts input without visible validation feedback, and the "Sign Up" button remains active even when the password may not meet the required criteria.

Current Behavior
The Sign Up button is enabled by default.
No real-time validation feedback is shown while entering the password.
Users can attempt to submit the form without knowing whether the password satisfies the stated requirements:
Minimum 8 characters
At least 1 capital letter
At least 1 special character
Expected Behavior
The password should be validated in real time.
Each requirement should be visually marked as met or unmet.
The Sign Up button should remain disabled until:
A valid email address is entered.
The password satisfies all listed requirements.
Appropriate error messages should be displayed when validation fails.
Steps to Reproduce
Open the Create Account page.
Enter a valid email address.
Enter a password that does not meet one or more of the displayed requirements (e.g., password123).
Observe that no validation feedback is displayed.
Click Sign Up.
Notice that the form allows submission attempt despite invalid password criteria.
Screenshots

Environment
Browser: Chrome (example)
Version: Latest
OS: macOS / Windows (as applicable)
Additional Context

The UI already displays password requirements, but there is no visible indication that these requirements are being validated. This may lead to user confusion and failed registration attempts. Enhancing client-side validation and user feedback would improve the sign-up experience.

[vansh2604-star]

/assign

Hi @Charushi06 , I would like to work on this issue under GSSoC'26.

I reviewed the issue and understand that the sign-up form currently does not enforce password requirements or provide real-time validation feedback. I would like to implement live password validation, requirement indicators, proper error handling, and disable the Sign Up button until all validation conditions are met.

Kindly assign this issue to me. Thank you!

[soma-prem]

/assign

[pallavghatvalwork-ops]

Hi @Charushi06, I am very interested in contributing to this issue for GSSoC'26.

I have analyzed the requirements and plan to resolve this by:

1. Implementing Local State: Tracking password criteria (minimum 8 characters, capital letter, special character) in real-time as the user types.

2)nDynamic Feedback: Adding visual indicators (e.g., color-coded status or checkmarks) to show which requirements are met.

3. Form State Control: Ensuring the "Sign Up" button remains disabled until both email validation and all password criteria are satisfied.

I understand others have already requested assignment, but I am ready to start immediately and would appreciate the opportunity to contribute to this fix. Please let me know if I can be assigned or if there is any other way I can assist. Thank you!