Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Responsive QR code component using HTML and CSS

accessibility
Damini Rajput•120
@GitDbR
A solution to the QR code component 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

  • lisztomania23•170
    @lisztomania23
    Posted almost 2 years ago

    Hello there! 👋

    I've taken a look at your code, and I have some feedback to share:

    • It seems you wanted to try and use absolute: position and transform: translate(-50%, -50%) to center the card within the .container. However, you could have achieved the same result more simply by using justify-content: center and align-items: center in the .container.

    • You've applied a media query for small screens to adjust the width of .items, the width of the img, and padding/margin for other elements. Instead of doing this, you could have given a non-relative width value to .items (width: 330px) and set the height: auto. But if you wanted to try and use a media query, you would need to make a few other tweaks.

    • It's a good practice to use a single <h1> element for the main heading of your page before using <h2>.

    • You've used a different font URL for "Outfit" font (which was recommended). Here's the corrected URL for the "Outfit" font: https://fonts.googleapis.com/css2?family=Outfit:wght@400;700&display=swap

    • I also made a few other tweaks to the fonts in <h1> and <p>, as well as the padding. Here is the code below:

    * {
        padding: 0;
        margin: 0;
    }
    
    body {
        background-color: hsl(212, 45%, 89%);
    }
    
    .container {
        width: 100%;
        height: 100vh;
        position: relative;
        display: flex;
        flex-direction: column;
    }
    
    .items {
        position: absolute;
        top: 50%;
        left: 50%;
        width: 330px;  /* changed value */
        /* width:25%; */
        height: auto;  /* changed value to auto */
        transform: translate(-50%, -50%);
        text-align: center;
        align-items: center;
        background-color: hsl(0, 0%, 100%);
        border-radius: 13px;
        padding-bottom: 20px;
    }
    
    .img {
        padding: 5px;
        margin-top: 20px;
    }
    
    img {
        max-width: 280px;  /* changed value */
        height: auto;
        border-radius: 10px;
    }
    
    /* changed h2 to h1; change in HTML also */
    h1 {
        padding: 6px 30px;  /* changed value */
        margin: 2px;
        color: hsl(218, 44%, 22%);
        /* font-weight: 700; */  /* import recommended font and activate this property */
        font-size: 22px; /* added */
    }
    
    p {
        padding: 6px 30px;  /* changed value */
        margin: 5px;
        color: hsl(220, 15%, 55%);
        font-size: 16px;  /* changed value */
        /* font-weight: 400; */  /* import recommended font and activate this property */
    }
    /* removed media query */
    

    Overall, your code is functional, but these improvements can help make it cleaner, more maintainable, and aligned with best practices. Keep up the good work! 👍

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