Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 15 days ago

Interactive and Responsive Login-Form with Email Validation

Vincent Dao•170
@Squ1nty
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?

In the end, I am most proud of being able to incorporate the JS validity requirements as expected; a simple and entry-level validation.

Next time, I would continue to work on developing my CSS responsive-ness skills to better build my website without having to go back and fix formatting issues at the end.

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

I encountered many challenges in this challenge actually. First, I had to deal with -webkit- issues that kept overriding my CSS, which I eventually learnt (through a good hour of reading) how to fix.

Regarding JS, I also encountered an issue with using the validity() method, only to realise I was missing the validityCheck() method call prior to using any other valid() methods. All issues were overcome through reading and learning of new materials.

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

Mainly, -since JS would be my weakest of the three-, what tips would you provide for my JS?

Secondly I would like specific help with SVGs, as in how would I make it more responsive and not fixed the way it is provided in a project?

Asides from this, any CSS responsiveness help would be highly appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Vincent Dao'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 1st-party linked stylesheets, and styles within <style> tags.

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.