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

Contact Form - Vanilla JS

Aakash Verma•9,500
@skyv26
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?

Did nothing special.

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

well, render the error message using javascript and I find a little tricky to color those radio and checkbox.

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

All feedback is valuable, and I appreciate suggestions that help me implement accessibility. Additionally, recommendations for checking my accessibility, such as screen reader announcements, would be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alexis•30
    @AlexisC73
    Posted 5 months ago

    This comment was deleted 5 months ago

  • Marzia Jalili•7,170
    @MarziaJalili
    Posted 5 months ago

    Hi @skyv26,

    The project's looking awesome!

    Some tiny adjestment you can consider implementing:

    • First, wouldn't it be better if the card had some margin at the top and bottom?

    You can set the font-size and gap between elements to smaller numbers to get rid of scrolling after updating the web with this detail.

    • Second, you can prevent the error boxes added by default.

    Take the code below as an example to use the preventDefault() function which removes them:

    btn.addEventListener("click", (event) => {
      event.preventDefault();
      // this ensuers that the boxes and other default styles 
      // will be removed
    });
    
    • In addition, when the user tries again to fill in the form it will be better if they were given cleaner layout. I mean without the error messages.

    Use the onChange function with the inputs to have the feature set.

    Other than this you're doing great!

    Keep up the grind💪

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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