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

password generator app

P
Jair•700
@JairRaid
A solution to the Password generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Habeeb Kareem•690
    @olaide-hok
    Posted 4 months ago

    Great work here! Some areas for improvement are

    1. The checkBoxesStates array and checkBoxes event listeners contain repetitive code for handling checkbox states. A loop or a more dynamic approach can be used to handle checkbox states.
    const checkBoxes = document.querySelectorAll("input[type='checkbox']");
    const checkBoxesStates = Array.from(checkBoxes).map((el) => ({
      category: el.name,
      isChecked: false,
    }));
    
    checkBoxes.forEach((el, index) => {
      el.addEventListener("click", (event) => {
        checkBoxesStates[index].isChecked = event.target.checked;
        checkLevelStrength();
      });
    });
    
    1. Hardcoded Values: The levelStates array and checkLevelState function use hardcoded values, making the code less flexible. Use a more dynamic approach to determine the strength level.
    const strengthLevels = [
      { level: 1, state: "TOO WEAK!", class: "too-weak" },
      { level: 2, state: "WEAK", class: "weak" },
      { level: 3, state: "MEDIUM", class: "medium" },
      { level: 4, state: "STRONG", class: "strong" },
    ];
    
    function checkLevelState() {
      if (passLength < 4 || passLevel === 0) {
        passStrength = "";
        return;
      }
    
      const level = strengthLevels.find((state) => state.level === passLevel);
      passStrength = level ? level.state : "";
    }
    
    1. Lack of Comments: The code lacks comments, making it harder for others (or your future self) to understand. Add comments to explain the purpose of each function and complex logic.

    2. Accessibility Improvements: The alt attribute for the copy icon (icon-copy.svg) is generic and doesn’t describe its purpose. The alt attribute for the arrow icon (icon-arrow-right.svg) is also generic. Use descriptive alt text for icons.

    <img src="./assets/images/icon-copy.svg" alt="Copy password to clipboard" id="copy">
    <img src="./assets/images/icon-arrow-right.svg" alt="Generate password" id="generate-icon">
    
    1. Missing for Attributes in Labels: The <label> elements do not have for attributes, which explicitly associate them with their respective inputs. Add for attributes to <label> elements.
    <label for="uppercase"><input type="checkbox" id="uppercase" name="uppercase">Include Uppercase Letters</label>
    <label for="lowercase"><input type="checkbox" id="lowercase" name="lowercase">Include Lowercase Letters</label>
    <label for="numbers"><input type="checkbox" id="numbers" name="numbers">Include Numbers</label>
    <label for="symbols"><input type="checkbox" id="symbols" name="symbols">Include Symbols</label>
    
    1. Typo in "STRENGHT" <p class="strength-text">STRENGTH</p>
    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