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

responsive newsletter form using flex-box

Dipesh•430
@Dipesh-sapkota1
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 challenges did you encounter, and how did you overcome them?

Customizing default behavior of form

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

I want to improve responsiveness of overall site.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ranit Manik•880
    @RanitManik
    Posted 12 months ago

    Your solution looks legitimate. I have reviewed your code, and here are some suggestions from me:

    1. Specify Image Dimensions:

      • Always set both the height and width attributes for images. This practice ensures that the space required for the image is reserved when the page loads, preventing layout shifts. Your success page is currently experiencing layout shifts because these attributes are not specified. For more details, refer to this article.
    2. Display User Email:

      • On the success page, ensure you display the user's previously input email. Currently, the email shown is always ash@loremcompany.com, which is incorrect.
    3. Alt Text for Images:

      • Avoid using alt text for non-decorative images. In this challenge, all images are non-decorative, so you should leave the alt attribute blank, like this: <img src="./assets/image.jpg" alt="">. For more information on this best practice, watch this video.
    • I hope you find my feedback helpful. Please mark it as helpful if you do.
    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
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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub