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

Contact Form with React/ React Hook Form/ Typescript

accessibility, tailwind-css, react
P
edpau•470
@edpau
A solution to the Contact form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

What I want to do

  • I am trying to use SVG to replace the default radio button to give my webpage a consistent look across different browser.
  • I want the SVG outer circle to grey out when it is not clicked
  • when the radio button is clicked (in my case, it is the label, I wrapped the label around the radio button), then colored when it is clicked

SVG I used has separate into parts for better control (please see in README)

What I read and try

  • I read Inclusively Hiding & Styling Checkboxes and Radio Buttons and learn to use opacity 0 over visibility for better accessibility.

    • using opacity 0 over sr-only can improve accessibility for users navigating by touch
    • Both display: none and visibility: hidden remove the element they hide from the DOM and accessibility tree
  • I learnt from this two code pen, using Vanilla CSS to style the SVG when the checkbox/ Radio button is clicked. Their SVG has separate into parts for better control using class name

    • #PracticalA11y: Inclusively-hidden custom-styled checkbox

    • CodePen Home Radio Button with SVG

    • SVG example (please see in README)

    • using Vanilla CSS to style the SVG when it is checked

    input:checked + svg {
        .radioDot,
        .radioOutline {
          opacity: 1;
        }
      }
    
  • I also learn from this example, Custom Radio Buttons with only Tailwind CSS, this example taught me to use Tailwind peer.

    • In Tailwind CSS, the peer-checked class can style elements that are siblings of the peer element when the peer element is checked.

Problem I have

  • I cannot control individual parts of the SVG using Tailwind
  • The peer-checked class will not work in my case because the element is not a direct sibling of the input element.
  • In Tailwind CSS, I cannot directly target sibling elements with complex selectors like input:checked + svg .radioDot because Tailwind CSS is a utility-first CSS framework that generates utility classes for individual elements.
 input:checked + svg {
     .radioDot,
     .radioOutline {
       opacity: 1;
     }
   }

How I solve it

  • I used a similar approach as https://marek-rozmus.medium.com/styling-checkbox-with-tailwind-46a92c157e2d
  • I put two SVG on top of each other and change their opacity.

Please suggest a better solution.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on edpau'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 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.