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

Contact Form using Less, keyboard navigation and vanilla Javascript

accessibility, less, bem
P
Yulia•720
@YuliaLantzberg
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?

Hello, Frontend Mentor Community,

This is my solution for the Contact Us Form.

Scored 100% on Google Pagespeed Insights! 🚀

🛠️ Built with:

HTML ✨ CSS 🎨 Less 💕 JavaScript 🧾

Fully responsive design crafted with a mobile-first approach 📲

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

Feedback is always welcome—let’s grow together! 🌱

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yosef shawah•200
    @yosefshawah
    Posted 7 months ago

    amazing solution Yulia!, looks like mobile design goes out of the card container, you can probably solve it with max-height or with setting height % on the content inside it within the media query, overall great solution way better than mine.

    Marked as helpful
  • AnDev•540
    @AnDevM
    Posted 6 months ago

    You can see my decision and give your opinion. Is it normal to do this?

  • AnDev•540
    @AnDevM
    Posted 7 months ago

    contactForm.reset(); find this method

  • AnDev•540
    @AnDevM
    Posted 7 months ago

    Congratulations! Super cool implementation logic that is hard to understand. But there is such a question, what should the form do after sending? In a real case, just overload the page? Please write an answer.

  • Abubakar sadiq•400
    @abubakar-sadiq001
    Posted 7 months ago

    You did a great job! but the main container height need to be set to zero

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

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

Oops! 😬

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

Log in with GitHub