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

Qr code component challenge using HTML and CSS

accessibility
Lokesh•110
@Lokesh8055
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?
  • Proud of Learning about frontend mentor rules for creating a project.
What challenges did you encounter, and how did you overcome them?
  • Encountered challenge with Readme file, it's a very good learning for me to create proper documentation
What specific areas of your project would you like help with?
  • Please go through my project and let me know on the areas that I can improve.
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted 8 months ago

    Great feedback above and we'll done for applying changes so quickly.

    I've got a few more recommendations:

    • get into the habit of including a full modern css reset at the start of the styles in every project. Andy Bell or Josh Comeau both have good ones you can look up and use.
    • Look up how and when to write alt text on images. There are some great posts about this in the resources channel on discord. Remember, alt is human-readable content not code. This image is really important, so needs a proper description. It needs to say what the image is (QR code) and where it goes to in this case (to FrontendMentor.io).
    • when building single components like this you still need to consider the context of where that component would be used in a real site. This card would never be used to serve the main heading on a page, so you know it shouldn't have a h1. Use a lower importance heading level like h2 instead.
    • it's better for performance to link fonts in the html head instead of css imports.
    • make sure the component can't hit screen edges by giving a wrapping element a little padding on all sides (eg body or main in this)

    Note the deployed link seems to be broken above so I can't preview the finished version at all.

    Marked as helpful
  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 8 months ago

    Hi, @Lokesh8055

    I checked out your solution and I have some thoughts:

    • Using height: 100vh on the body is okay for this challenge, but I'd recommend using min-height: 100vh instead. This approach ensures that the body will expand if the content overflows, which is helpful in most cases (though there are some exceptions). Try applying this in future challenges as well.
    • Consider making your class names more descriptive. For instance, class names like .improve and .skills don’t clearly convey what they’re styling, which can make your code harder to understand and maintain, especially if the text content changes. It might help to research CSS naming conventions (like BEM or utility classes) for more inspiration.
    • The combination:
    section {
      max-width: 100%;
      width: 320px;
    }
    
    

    may not work as intended. Instead, try:

    section {
      max-width: 320px; /* Using rem units here can improve scalability */
      // You don't need max-width: 100% since section is a block-level element
    }
    
    

    This will allow the section to adapt better to different screen sizes. Using rem instead of px for the max-width also improves scalability, making it easier to adjust based on the user's font size settings. For this challenge, I think it's fine, though.

    Hope this helps!

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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