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

Responsive Newsletter Sign-up Form with Email Validation

P
Jayco•470
@jayco01
A solution to the Newsletter sign-up form with success message 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 proud of figuring out how to properly validate an email input using HTML forms, CSS pseudo-classes (:invalid, :focus), and JavaScript regex. Initially, I struggled with displaying the error message and highlighting the input field, but after reworking my approach, I successfully implemented a clean validation system.

I want to further improve my JavaScript skills, especially in handling form validation logic and optimizing event listeners. Next time, I’d focus on writing cleaner, more efficient JavaScript while exploring different validation techniques.

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

The biggest challenge was figuring out how to validate the email input correctly using HTML, CSS, and JavaScript. Initially, I struggled to display the error message and highlight the input field when the email was invalid.

How I Overcame It:

  • I learned that the <form> element is required for built-in validation to work properly.
  • I integrated CSS pseudo-classes (:invalid, :focus, :not) to style errors dynamically.
  • I restructured my JavaScript to use regex for validation, .add() and .remove() for class toggling, and checkValidity() for cleaner validation logic.

After redoing my entire HTML, CSS, and JavaScript, I was able to create a fully functional validation system that works smoothly across different screen sizes.

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

I used :invalid, :focus, and :not to handle input validation styling. Are there more efficient or scalable ways to manage form error styling in CSS?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amol Vyas•170
    @amolvyas-6
    Posted 5 months ago

    success page is using dummy email instead of actual one

    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

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