Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Contact Form with vanilla JavaScript

Jay L•80
@jaylchive
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?

Trying out radio and checkbox input types that it wasn't familiar to me was the best experience I had from this challenge. It was quite challenging but definitely worth trying. If I didn't challenge myself with it, I would have made a custom radio button and checkbox.

I think it's crucial to keep on challenging yourself and get out of your comfort zone to grow new skills. That's what I've learned from this challenge.

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

Working with input types(applying custom styles, manipulating programmatically) was a bit challenging. I wasn't happy with myself that I didn't even know how and where to start with and I've started programming for quite amount of time. I had to google it and adjust the code.

But I think it's better to learn even if though you think is late than not knowing at all.

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

Any feedback would be grateful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Umar094•280
    @Umar094
    Posted 12 months ago

    form validate code is good I see, don't know about inside) but it better then others

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