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

Responsive contact form

accessibility, animation, lighthouse, van-js
saccoViola•90
@saccoViola
A solution to the Contact form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ibrahim Morad•380
    @IbrahimMurad
    Posted 5 months ago

    Looks good. But you need some adjustments for better results.

    1. Add novalidation to the form since you are validating manually.
    2. Remove the action attribute; you are not making any requests.
    3. The event listener should be 'submit' on the form, not the 'click' on the button.
    4. aria-descripedby takes the id of the error element; you passed the id of the same element.
    5. Since you added required to the inputs, you just need to use inputElement.validity.valid to check if the value is valid (in this case, it will ensure that the value is provided and the email is a valid email).
    6. Give each label for the radio input a unique for value (for example, the value itself - general or support-), then add an id with the same value so that when you click on it, the value is selected.
    7. I noticed that you, sometimes, uses <br />, it works but you can wrap the elements that you want in the same line and use CSS to style it to stay in the same line, and also with CSS make sure the next element is in its own line.
    8. some other styles are missing, but I think its fine.

    Let me know if you need more clarifications.

  • Ilham Bouktir•500
    @ilham-bouk
    Posted 4 months ago

    Good solution for this challenge.

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