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

Responsive Contact Form Using Vite, TypeScript, and SASS

Achi Gyuse Achi•490
@Achigyus
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 learned how to setup a typescript project in vite and also how to use sass to write less css code through rule nesting

Some code I'm proud of:

.query_wrap
  border: 1px solid vars.$gray_500
  border-radius: vars.$spacing_1
  padding: 0.75rem 1.5rem
  font-size: 1.125rem
  line-height: 1.5
  color: vars.$gray_900
  display: flex
  gap: 0.75rem
  align-items: center
  flex: 1 1 0%

  &:hover
    border: 1px solid vars.$green_600

  label
    font-size: 1.125rem
    line-height: 1.5
    color: vars.$gray_900
    cursor: pointer

  &:has(input[type="radio"]:checked), &:has(.querytype_input:focus-visible)
    background-color: vars.$green_200
    border: 1px solid vars.$green_600
window.scroll({
  top: 0, 
  left: 0, 
  behavior: 'smooth'
})
What specific areas of your project would you like help with?

The accessibility

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Simon Hickling•550
    @SimonHickling
    Posted 3 months ago

    This is very good work here. The only minor thing is that the original had an input:focus rule, giving the input fields a thicker and darker green outline. Apart from this, excellent work. I struggled with the radio and checked button icons, and ended up going about it a clumsy way, but yours seem perfect!

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