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

basic html and css web-design

accessibility
0-scripter•10
@0-scripter
A solution to the QR code component 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?

this is my first time writing a code, hence I am very happy for trying my best and completing this task.

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

reading material is different than applying it in real project u just get blank, so the only solution is keep practicing and coding.

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

my code is not clean, I want to know how I can make it shorter and more clean. Any other opinion will also be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rora Alem•370
    @Rgit915
    Posted 8 months ago

    Hi @0-scripter,

    I reviewed your code, and you've done a great job so far! I have a few suggestions that could make the solution even cleaner and more aligned with best practices:

    Semantic HTML Usage:

    Consider using meaningful headings like <h1> or <h2> for titles instead of <p> tags. This helps with both readability and accessibility. Group related elements using meaningful containers like <div> or <section> for better structure and styling.

    CSS organziation:

    Move the inline CSS(in index.html) for .attribution into the your external css.css file to separate concerns.

    Alt Text Improvements:

    Avoid repeating the image file path in the alt attribute. Instead, describe the image's function. For example:

    alt="QR code to visit Frontend Mentor"
    

    Ensure that the alt attribute accurately describes the purpose of the image rather than the file path.

    Personalization:

    Update "Coded by <a href="#">Your Name Here</a>" with your actual name to make the footer more personalized and authentic.

    Remove Repeated Lines:

    Lines 29 to 30 appear to repeat the content already found in lines 43 to 46. You could remove lines 29 to 30 to avoid duplication.

    These tweaks will improve your code’s readability and accessibility. Keep up the great work! 😊

    Best regards,

    Rora

  • océane•290
    @Ocece77
    Posted 8 months ago

    Code Review for Your Frontend Mentor Challenge ✨

    1. File Naming Convention 📂:
      Usually, the main stylesheet is named style.css by convention, just like the main HTML file is typically named index.html. It’s a good practice to follow this approach and name additional files based on their specific purpose. It keeps your project organized and professional! 🗂️

    1. Text Structure Improvements ✍️:
      • At line 29, your text "Improve your front-end skills" looks like it’s the main title of your card. It would be better to wrap it in an <h1> tag to reflect its importance. Here's an idea for the CSS styling you could use:
    h1 {
      font-weight: bold;
      font-size: 26px; /*or maybe 24px 🧐*/
      color: hsl(218, 44%, 22%);
    }
    
    • For the smaller text below, it seems like a descriptive paragraph. Use a <p> tag for semantic correctness. Here's a suggestion for the CSS:
    p {
      font-size: 15px;
      font-weight: bold;
      opacity: 0.5; 
      /* or alternatively */
      color: hsl(212, 45%, 89%);
    }
    

    🎯 This approach makes your structure more accessible and easier for other developers (or you!) to read later. 👓


    1. Rounded Corners 🌟:
      Nice job with the rounded corners! 🥳 However, pay close attention to details—it looks like the QR code image also needs rounded edges. A quick CSS fix should do the trick:
    img {
      border-radius: 8px; /* Adjust value based on design specs */
    }
    

    🎨 Do not forget the background color that was in the style-guid was hsl(212, 45%, 89%)


    1. Attention to Detail Matters 💡:
      You’re doing great, but don’t forget to double-check the design specifications! 🔍 Take a close look at the style-guide.md file provided by Frontend Mentor. It’s your best friend for nailing the exact look and feel. 💪

    1. Planning Ahead 📝:
      Before jumping into coding, try to map out your project:
      • Sketch your layout 📄.
      • Identify the key elements you’ll use, like divs, headers, paragraphs, etc..
        This process will make the implementation smoother and more organized. 🎯

    Amazing effort! 🎉 Don’t feel discouraged by small mistakes—they’re part of the journey. Keep practicing, and soon you’ll be creating stunning, pixel-perfect designs in no time. 🚀 Remember: details make all the difference! 🌟 You’ve got this! 💪

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