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

Accessible contact form | Semantic HTML, vanilla JS & CSS

P
Jonatan Samuelsson•540
@jonatan-samuelsson
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?

Form validation became unneccessarily complicated, as I set out to do it with HTML and CSS only. I got it working to 90% but I couldn't make it the final stretch. I could have left it and it would have been working fine, but it would not have been able to differentiate missing from incorrectly provided inputs. In the end, I scrapped it and implementet an all out JS solution in stead, which all took way too long and didn't exactly end up DRY.

On the accessibility side of things, the provided articles on accessible forms wer super helpful and well-curated. Implementing error messages and validation really makes you have to think about how it all comes accross to AT:s.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • T23harms•540
    @T23harms
    Posted 3 months ago

    The code appears to be a clean, well-structured contact form with proper HTML, CSS, and JavaScript integration. The form is responsive, and CSS variables are well-organized for easy adjustments. The JavaScript uses event listeners to handle form validation and user interactions, ensuring that required fields are validated and users get real-time feedback.

    A few things to note:

    It’s good that validation functions are modular, making it easy to add or modify rules. However, make sure to check for edge cases like special characters in names that might not pass the current regex.

    The use of ARIA attributes is a good accessibility practice, but adding labels for all interactive elements would further improve accessibility.

    The success message has a nice animation but ensure it doesn’t interfere with form usability on slower devices.

    Overall, it's a well-implemented solution that prioritizes user experience and responsiveness.🚀

    Marked as helpful

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, SASS, 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