Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Newsletter Signup

accessibility
Ally Glenday•20
@ally-glenday
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


First submission using HTML, CSS & JavaScript - so any help / feedback would be amazing!

I wanted to have the user's input (email address) displayed back to them on the sucess page, but I can't seem to be able to show it using the DOM. I saved it as a variable and I can console.log it / alert their email on the success page, so I know this can be done. However, when I try to convert this into an HTML element, e.g. <span> or <p> to be shown on the page instead of 'ash@loremcompany.com', it doesn't seem to work.

If anyone has any ideas why this is, I'd hugely appreciate it!

Thanks :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Azzy dvyastia kesuma•1,425
    @azzykesuma
    Posted over 1 year ago

    congratulations on completing the challenge! you can use localstorage to set the email for the purpose of this challenge https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage then, get the localstorage value, and inject it into DOM

    but in the real job scenario, i think you need to store it in some sort of database

    Marked as helpful
  • Wasiu Mustapha•40
    @Datom969
    Posted over 1 year ago

    To make the email input value show on the submit page, create an empty <span></span> where the email value should be in your html, give it an id( say mymail). In JavaScript, get the id. Then, to display it use DOM manipulation: mymail.innerHTML = " " + input.value +". " Then, for the dismiss button don't forget to set input.value to empty, so it doesn't show in the input field again. Check my js code for clarity.

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 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

Oops! 😬

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

Log in with GitHub