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

QR Code Component with HTML and CSS

Raihan•20
@erkatia
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

  • Hassia Issah•50,390
    @Hassiai
    Posted over 2 years ago

    Replace<div class="container">with the main tag, <p class="bold"> with <h1>and <div class="attribution"> with the footer tag to fix the accessibility issues. click here for more on web-accessibility and semantic html

    To center .container on the page using flexbox, add min-height: 100vh to the body. There is no need for align-content in the body. flexbox has no align-content rather its grid that has align-content.

    To center .container on the page using flexbox:
    body{
    min-height: 100vh;
    display: flex;
    align-items: center;
    justify-content: center;
    }
    

    there is no need for position absolute and it properties in .container to center .container.

    Give .container a padding value for all the sides and give the img a max-width of 100% and a border-radius value, the rest are not needed.

    Give h1 and p the same font-size of 15px and the same margin-left, margin-right and margin-top values. Give p a margin bottom value.

    Use relative units like rem or em as unit for the padding, margin, width values and preferably rem for the font-size values, instead of using px which is an absolute unit. For more on CSS units Click here

    Hope am helpful.

    Well done for completing this challenge. HAPPY CODING

    There is no need to us p

    Marked as helpful
  • Sandro•1,150
    @sandro21-glitch
    Posted over 2 years ago

    Hi Erkatia

    Here are a few suggestions for improvement your code

    Use semantic HTML elements:

    Instead of using a div with a class name "container", you can use a section element to wrap the QR code and text content, as it is a stand-alone content block that has a distinct purpose.

    Add alt text to the QR code image:

    For accessibility purposes, it is important to add a descriptive alt text to the QR code image. This will be read by screen readers to provide information to visually impaired users.

    Consider using a CSS reset or normalization stylesheet: This will help ensure that the styles of your website are consistent across different browsers.

    Use CSS variables:

    Consider using CSS variables to store values that are used multiple times in the stylesheet, such as font family, font size, and colors. This makes it easier to update the styles across the whole stylesheet if needed.

    Minimize the use of absolute positioning:

    absolute positioning can make it difficult to maintain the layout of a page. Consider using other layout techniques, such as flexbox, to achieve the desired layout.

    Consider using rem units for font sizes: rem units are relative to the root element (HTML), and make it easier to maintain consistency in font sizes across the page.

    Happy Coding

    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.

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