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

Responsive Contact Form - HTML/CSS/JS

accessibility, bem
Luqman (Luke)•320
@luqmanx1998
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?

Returning from about a month break from building projects with a newfound knowledge of Javascript!

This small but functional contact form was a fun project to start implementing a little bit of JavaScript, which is a step up from my previous HTML/CSS-only projects! I learned quite a bit with this one. It's got a clean design and it's fully functional, and I am satisfied with this one!

What challenges did you encounter, and how did you overcome them?
  • Form Layouts: I actually don't have much experience with form building prior to this challenge. This form is my first actual form that I've built from scratch! Although I have the knowledge to build it, putting that knowledge into practice was a different matter, but I'm glad I was able to do just that, with a bit of patience :D

  • JavaScript: Since this is my first project where I actually implement some JavaScript, instead of the usual HTML/CSS, it was still a bit time-consuming, as I hadn't developed the muscle memory for this. But I still managed to put my knowledge to practice and it turned out okay! Going forward, I am much more confident and will continue to get better and faster. I'm also aware that my code is not the cleanest, or optimised, but I'll let this one slide as my first challenge with JS incorporated, and I'll make it much better on the next one. Also, I was doing this project without a figma file, just purely guessing the dimensions, so I'm guessing before I post this, that my solution would look pretty different, and that's okay 😂. Really, I just wanted to practise Javascript more in this one.

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

Any feedback at all would be very much appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Luqman (Luke)'s solution.

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.