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

QR Code - first FEM challenge

Gustavo Atanazio•80
@gustavo-atanazio
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,410
    @Hassiai
    Posted over 2 years ago

    Replace <div class="container"> with the main tag, <span class="title"> with <h1> 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.

    For a responsive content, there is no need to give .container a height value and replace its width with max-width. Give the img a max-width of 100% and a border-radius 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

    Marked as helpful
  • RabicaTahir•500
    @RabicaTahir
    Posted over 2 years ago

    Asalam o Alaikum! @gustavo-atanazio. 🎯Congratulations on completing the challenge !

    💬I have some suggestions about your code.

    HTML 🔔:

    ▪ It is advisable that you place all your main site content in a landmark element <main>. Wrap the body code in main tag.

    Click & Wrap the code

    <div class="container">

    ▪ Best practice is to ensure that the beginning of a page's main content starts with a h1 element.

    Click & Replace

    <span class="title">Improve your front-end skills by building projects</span>

    CSS: 🎨

    📍▪ Instead of using pixels in font-size, using relative units like em or rem is a good practice.

    I hope you find it useful! By the way, the solution was great. 🙌💯

    Enjoy coding, Stay Safe! 🤞

    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