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

Mobile first newsletter signup form [HTML, CSS, JS]

accessibility, lighthouse
Shanto Paul•130
@shantoopaul
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?

This one took longer than I expected—mostly because I was trying out new things, like learning how Lighthouse works and understanding metrics like FCP, LCP, FB, etc. I'm proud that I got to explore concepts I hadn't worked with before. Next time, I'd like to use PostCSS, and also try out Eleventy (11ty) to see how much it can improve site performance.

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

Most of them were small issues, like rel=preload not working for images—which turned out to be a typo issue. I also had to figure out what the table version of the layout would look like. Another problem was that the transition on the button’s background color wasn’t working because it was a gradient color, and transition doesn’t apply to gradients. To work around that, I used a ::before pseudo-element to create the gradient background and then adjusted the opacity to achieve an ease-in-out effect.

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

I’d love to get feedback on my code performance—whether what I’ve done is correct or if there are any issues I might have missed. Specifically, I’m looking for feedback on things like code optimization, form validation, and accessibility.

That said, I’m open to any suggestions for improvement :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anderson Ken Ishiba•120
    @ishibak
    Posted 14 days ago

    Are you studying by yourself? Look's very good.. Hope i get used to javascript fast too.

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