Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 30 days ago

Interactive Sign Up form

Ahmed Ali•550
@qayoommunawar
A solution to the Contact form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

i created custom radio buttons and checkbox, was hard but i did it.

What challenges did you encounter, and how did you overcome them?

creating custom radio and checkbox was a real headache, but i by using different references and resources i overcame.

What specific areas of your project would you like help with?

how i can make form more interactive ?? js is a mystery can always be improved. How can i check when user is inputting data weather it is valid or not and show an error ???

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,550
    @thisisharsh7
    Posted 29 days ago

    Fantastic work! Great job using references to overcome challenges while adapting solutions to your code.

    To make the form more interactive and improve validation:

    1. Real-time validation: Add event listeners for input events to check data as the user types. For example:
       firstName.addEventListener('input', () => {
         firstName.nextElementSibling.classList.toggle('hidden', firstName.value.trim().length >= 4);
       });
    

    This shows/hides errors instantly.

    1. Visual feedback: Add a green border or checkmark for valid inputs using a class like .valid { border-color: var(--color-green-600); }.

    2. Disable submit button: Disable the button until all fields are valid using button.disabled = !isValid;.

    3. Responsive improvements: Use rem for padding/margins (e.g., padding: 1rem) and media queries to adjust .wrapper width for smaller screens.

    Good work overall-Keep experimenting!

    Marked as helpful
  • Marzia Jalili•7,750
    @MarziaJalili
    Posted 29 days ago

    You're crashing it! 🔥

    🌟 Tweaks?

    ✅ You could simply use the property below for the radio buttons and checkbox to change the color instead of building everything from scratch yourself:

    accent-color: green; 
    

    ✅ On mobile, the size and position of the success box are a bit off, bro. Like we hit the submit button, waiting for something to pop up, but nothing is there unless we scroll back to the top.

    ✨ Here's how to fix this:

    • set the width to a larger number to avoid too match stretching.

    • change absolute positioning to fixed to make it show up all across the page.

    • we will add a nice little animation for better user experience. 😀

    width: 94%;
    position: fixed;
    /* Fun stuff */
    transform: translateY(-10%);
    opacity: 0;
    transition: 1s;
    animation: pop-up 1s ease-in 1 forwards;
    
    @keyframes pop-up {
      to {
        opacity: 1;
        transform: translateY(0%);
      }
    }
    

    Other than that, the code is just flawless!

    😎😎😎

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub