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

Contact Form Validation With ReactJS, and TailwindCSS

react, tailwind-css, vite
Kareem Ayman•270
@kareemayman
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?

It was my first time using Tailwind, ReactJS, React-Hook-Form

Despite The project being very simple, It took my few days to finish, It was a good learning experience, I had fun applying What I've learned recently.

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

Problem 1: After Submitting the data, I need to press on consent checkbox 3 times to toggle it again

Problem 2: Pressing tab doesn't focus on queries section

Any feedback would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,720
    @markuslewin
    Posted 7 months ago

    Hi!

    I think your consent checkbox counts as a controlled component, since you rely on the value to render the component. This means you have to provide defaultValues for it to reset properly:

    export function Form() {
      const { watch, reset } = useForm({
        defaultValues: {
          consent: false,
        },
      });
      return <></>;
    }
    

    Pressing tab does focus the queries section, but it doesn't check the radio buttons. That's how native radio buttons work, so I actually don't think that's a bug. You could add some focus styles for the radio buttons to make it clearer what's happening:

    export function Query({ enquiry, value }) {
      return (
        <label
          className={`
            has-[:focus-visible]:outline has-[:focus-visible]:outline-offset-2
            ${
              enquiry === value
                ? "bg-green-100 border-green-700 before:bg-green-600"
                : ""
            }`}
        >
          <input type="radio" />
        </label>
      );
    }
    
    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, 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