Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Responsive Form with Javascript Form Validation

Elizabeth Okuta•150
@Mimieveshofuo
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedbacks would be appreciated. Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Michael Adebambo•1,045
    @Blazing-Mike
    Posted almost 3 years ago

    Great job you did here. Everything looks perfect, the only suggestion i have is the password input; it accepts an input of even two characters, in the password validation you can add that it returns an error for password <= 6 characters. If you want to go further you can add that it contains a combination of letters or symbols and numbers. Well-done Elizabeth

    Marked as helpful
  • P
    Luciano Lima•1,270
    @LucianoDLima
    Posted almost 3 years ago

    Good job on finishing this project!

    A few suggestions:

    • Your div currently stretches as much as I can zoom out, you can avoid that by adding a max-width: ; in your .wrapper. For example max-width: 1440px;.

    • Your input's border is complete black, which makes so you can't really notice when the focus pops up once you click it. You could try implementing the :focus element. It would go like this:

    You go in your CSS file and instead of hsl, you add hsla, which makes so you can change the opacity of your border, in this example I changed it to .4 (40%) -> input { border: 1px solid hsla(249, 10%, 26%, .4); . Then you could write input:focus { border-color: black }, that way when you click on your input to write something, it will change the borders to black, and when you click away, it will change back to a weaker black, hope that makes sense.

    • You could do the same as i mentioned above to the placeholder, since it is a very strong black instead of a weak one like in the design. To do that you could add input::placeholder { opacity: .5; } .

    Happy coding!

    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