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

Responsive qr code component using mobile first workflow

accessibility
sanket kumar•300
@sanketcharanpahadi
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone, I have a doubt that the img element is inline but I can set my width and height . Can anyone help me out because we cannot set width to inline elements . so what is wrong here ?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kacper Kwinta•1,405
    @kacperkwinta
    Posted over 3 years ago

    Some tips:

    • Try to avoid static height, because on small screens text in box just overflow in bottom
    • Page should contain a level-one heading
    Marked as helpful
  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! Nice work with this project! Looking at your solution, I think you should considered the following as well...

    • Import the attribution style in the CSS file and remove style tag
    • Include description to the alt in img tag and should not be empty
    • Wrap the attribution with specific tag like footer for readability
    • Alternative way to set size on the image is to create a rule set that includes the tag property for example...
    HTML:
    <div class="img">
              <img src="./images/image-qr-code.png" alt="" class="qr" />
    </div>
    
    CSS:
    .img img.qr {
         width:100%
    }
    
    

    The issue would be you wrap the img first with .img class then add another class within the img... the width would not be distinguish properly.

    Hope this helps and Keep it going!

    Marked as helpful
  • Account deletedPosted over 3 years ago

    Hi there 👋

    Congratulate on finishing your project 🎉. The design looks beautiful 😃.

    I will try to answer your question and hope it helps you. Img tag is not a strictly inline element, it's a replaced-inline element. Because <img> is an inline tag, that is replaced by its own source file (well, it's still an inline element). See these links for more information MDN

    Happy coding ☕

    Marked as helpful
  • sanket kumar•300
    @sanketcharanpahadi
    Posted over 3 years ago

    Thank you for resolving my issue.

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

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