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

HTML,CSS,CSS Flexbox,CSS Form Validation,Javascript

Otabek Sotvoldiev•30
@BekCodingAddict
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’m most proud of successfully implementing form validation using only HTML and CSS, without relying on JavaScript. It was a challenge to ensure the error messages only appear after the user submits the form, but I managed to achieve this using :invalid selectors creatively. Additionally, making the radio button selection visually clear with CSS enhancements was a great learning experience.

Next time, I would focus more on browser compatibility to ensure the validation styles work consistently across different devices. I would also explore ARIA attributes to improve accessibility and make the error messages more user-friendly for screen readers. If JavaScript were allowed, I might add more interactive validation feedback to enhance the user experience.

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

One of the main challenges I faced was ensuring that the error messages only appeared after the user clicked the submit button, rather than showing them by default. Since I was using only HTML and CSS for validation, I had to carefully structure my CSS selectors. I overcame this by using the :invalid pseudo-class effectively and ensuring that error messages were hidden initially but displayed when necessary.

Another challenge was handling radio button validation because the error message needed to appear outside the .radio-box, making sibling selectors (~) ineffective. I resolved this by rethinking the structure of my HTML and styling the closest possible container using CSS.

Additionally, making the form fully responsive using CSS Flexbox required careful adjustments, but through testing and tweaking, I managed to ensure a smooth layout on different screen sizes.

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

I would love feedback on the form validation approach using only HTML and CSS. Specifically, I’d like to know if there are better ways to structure the form and selectors to improve accessibility and maintainability.

Additionally, I faced some challenges with radio button validation since the error message needed to be placed outside the .radio-box. I’d appreciate suggestions on handling this scenario more efficiently using just CSS.

Lastly, any feedback on improving responsiveness and making the UI more polished, especially for smaller screens, would be really helpful!

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 Otabek Sotvoldiev'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

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.