Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Contact form with form validation and Animated success modal

accessibility, animation
Tony•100
@TonyHansord
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 started this challenge as I haven't done one in while, not since before I started my bootcamp. I wanted to go back to the fundamentals and test what i have learned since.

As this was a frontend only version I decided to just use vanilla JS and CSS.

Initially I thought that using React would be overkill for a simple form component. But looking at and modifying the form elements individually, I could see the case for creating reusable form components. Maybe in a another challenge or next crack at this, I will try that.

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

Surprisingly the most difficult thing I found was changing the checkbox and radio button checked images. I have never had to do this before. After some research I found out that you need to set the image as a background to the label linked to the checkbox. The code for css is below.

.consent input[type='checkbox'] {
  height: 1rem;
  width: 1rem;
  appearance: none;
  border-radius: 0;
  border: 1px solid var(--primary-medium);
}

.consent input[type='checkbox'] + label {
  background: var(--neutral);
  background-repeat: no-repeat;
  display: inline-block;
  cursor: pointer;
}

.consent input[type='checkbox']:checked {
  background-image: url(/assets/images/icon-checkbox-check.svg);
  background-size: cover;
  background-repeat: no-repeat;
  border-color: transparent;
} 
What specific areas of your project would you like help with?

I would like to know how to improve the accessibility of the form, for example: users of screen readers

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Tony's solution.

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.