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

Responsive Newsletter with Authentication using JavaScript and Native

Carlos Damota•120
@carlosdamota
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 am most proud of implementing secure DOM manipulation by avoiding innerHTML and instead using document.createElement and append. This approach enhances security and prevents potential XSS vulnerabilities. Additionally, I focused on accessibility improvements, such as using role="alert" and aria-live="assertive" to enhance the user experience for screen readers.

Next time, I would refine focus management even further to ensure a seamless navigation experience, especially for keyboard users. I would also explore implementing a lightweight state management solution to handle form validation and UI updates more efficiently.

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

One major challenge was ensuring that the form validation messages were properly announced by screen readers. Initially, they were not being detected, which led me to research ARIA attributes more thoroughly. By adding aria-live="assertive" and structuring the validation messages correctly, I was able to resolve the issue.

Another challenge was managing the dynamic success message while maintaining a smooth user experience. To solve this, I ensured that focus was shifted to the dismiss button when the success message appeared, allowing users to close it easily using the keyboard.

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

I would appreciate feedback on:

Accessibility Enhancements – Are there additional improvements I could make to further enhance the accessibility of the form?

CSS Nesting and Maintainability – I used native CSS nesting to improve readability. Is this approach effective, or would there be a better way to structure my styles?

Performance Optimization – Given that this is a simple form, are there any optimizations I could make to enhance performance, especially regarding JavaScript execution?

Any insights or suggestions on these areas would be greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David Mwalimu•260
    @broken555wheel
    Posted 4 months ago

    Amazing job.

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