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

Contact form

accessibility, pure-css, van-js, jquery
EmicJoykiller•270
@EmicJoykiller
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?

I'm most proud of how I recreated a polished, fully functional contact form without using any libraries or frameworks — just pure HTML, CSS, and JavaScript. It closely follows the original design while being clean, responsive, and accessible. Next time, I would consider adding animations (like fade-ins for success messages) and improving keyboard accessibility even further, for example by adding focus styles or live ARIA updates for form validation errors.

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

One of the main challenges was handling form validation manually without relying on built-in browser error popups or external libraries. To overcome this, I wrote a custom validation function that checks each field, shows or hides specific error messages, and provides instant feedback to the user. Another challenge was maintaining a responsive layout that adapts well to smaller screens without using a CSS framework like Tailwind or Bootstrap. I solved this by using simple flexbox layouts and media queries to ensure the form remains user-friendly on all devices.

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

I would love feedback on:

Best practices for form validation: Is there a more efficient or scalable way to handle field validations without repeating similar code?

Accessibility improvements: How can I make error messages and success notifications more screen-reader friendly (e.g., using ARIA attributes)?

Code organization: Are there better ways to structure the JavaScript for easier maintenance if the form gets more complex in the future?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gustavo Gutiérrez•360
    @gustavo2023
    Posted about 1 month ago

    Hi, I this are some suggestions to improve your code:

    • Consolidate Validation Logic: The validation checks for each field are very repetitive. You can create a more generic validation function or loop through a configuration object.
    • Separate Concerns: Keep DOM manipulation (show/hide errors, success message) separate from the core validation logic.
    • Error Handling Robustness: Add checks in showError and hideError to ensure the [data-error="..."] element actually exists before trying to access its style property.

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