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

Responsive QR Code

sass/scss
hkaur108•310
@hkaur108
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?

I have tried to use correct semantic for my project and tried making it responsive as much as I can using SASS.

What specific areas of your project would you like help with?

Any feedback is welcomed to make my project accessible and responsive.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rebecca Padgett•2,100
    @bccpadge
    Posted 7 months ago

    Hi @hkaur108. Congratulations on completing this challenge!!!🎉

    You are on the right track and need to focus on using semantic HTML tags.

    HTML 📃:

    • Every website must have at least one landmark like a <main> tag.
    • Wrap your content using the <main> tag and attribution info in a <footer> tag.
    • Alt Text for Images: Always include descriptive alt text for images. This ensures that screen readers and other assistive technologies can understand what the image represents, making your content more accessible.

    Example:

     <img src="./images/image-qr-code.png" alt="Scan the qr code to visit frontendmentor.io website">
    

    CSS 🎨:

    • Media query does not need to be used in this simple project.
    • Look at the styleguide.md file that give in the starter files provided from Frontend Mentor with the correct font-family.
    • Best practice to only apply CSS styles that are needed.
    • Max-width:100% and display:block; are great reset for images in CSS.

    Text-algin: auto; is a invalid CSS property. When building these projects be sure to use Developer Tools.

    .text-container {
      width: 100%;
      text-align: auto;
    }
    .text-container {
      width: 100%;
      text-align: auto;
    }
    

    Here is my solution to this challenge: QR Code component

    I hope you find these tips useful! Don’t hesitate to reach out if you have any questions or need further guidance. Keep up the amazing work!

    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

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