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

Password Generator App built with HTML, CSS, JavaScript

accessibility
Christina•240
@codercreative
A solution to the Password generator app 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'm happy with how user-friendly and visually appealing the app turned out. One thing I noticed is that the Figma design did not include a reset button, which is a feature I could consider adding later to enhance usability.

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

Coding the password strength level in JavaScript was a bit of a challenge and so was styling the checkboxes in CSS.

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

I’m open to any helpful feedback, particularly in areas like improving my JavaScript logic or optimizing the code for better performance.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Mina Makhlouf•1,150
    @Minamakhlouf
    Posted 3 months ago

    This project was very well done. I liked how the output changes on each change of the slider and checkboxes as well as how it shows error messages right when they happen on the output field.

    I found styling the slider especially difficult but how I dealt with this was making a custom slider that was designed with just <div> elements and I put it on top of the original slider <input> component and using JavaScript to move them at the same time.

    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