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

Basic HTML and CSS only.

Utkarsh9571•640
@Utkarsh9571
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 think the answer to this question is not that i completed this challenge, but the fact that i started making projects, i completed java 2 days ago and then struggling with git and github, but now i started.

What challenges did you encounter, and how did you overcome them?

I completed HTML and CSS 2 weeks ago and didn't practice them, so i need to take help from youtube and i was able to recall most of the components of HTML and CSS.

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

I was wondering if i need to revisit the HTML and CSS course, but i think not, i was good during the course, first i wanna try some more challenges and then i will see if i need to do a revisit or not, hopefully not.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted 2 months ago

    Hi, well done!

    Here is a bit of feedback. I hope you find it clear and helpful. For maximum learning, I highly recommend applying these changes before moving on to the next project.

    Good luck :)

    HTML:

    • Every webpage needs a <main> element that wraps all of the content, except for <header> and footer>. This is vital for accessibility as it helps screen readers identify a page's "main" content. Change .container to a <main>.

    • The alt text must also specify where it leads(the frontendmentor website). A good alt text would be "QR code leading to the Frontend Mentor website."

    CSS:

    • Make a habit of including a modern CSS Reset at the top of your stylesheet. At least include the following snippet:
    *,
    *::before,
    *::after {
      box-sizing: border-box;
    }
    

    MDN has good articles about the CSS Box Model and the box-sizing property.

    • I recommend adding a bit of padding, for example 16px, on the body, to ensure the card doesn't touch the edges on small screens.

    • There's a typo in your font-family declaration. font-family : 'Outfit', sans-serief; should be font-family : 'Outfit', sans-serif;.

    • Remove the styles on .container, they are not needed.

    • Add justify-content: center on the body to center the card horizontally.

    • Descendant selectors like .text h2 increase specificity, making the styles harder to override. Instead, give elements a class and use that as the selector.

    • Remove the margin on the card.

    • Add a max-width of around 20rem on the card to prevent it from getting too wide on larger screens.

    • font-size must never be in px. This is a significant accessibility issue, as it prevents the font size from scaling with the user's default browser setting. Use rem instead.

    • On the image, add display: block, height: auto and change width to max-width: 100% - the max-width prevents it from overflowing its container. Without this, an image would overflow if its intrinsic size is wider than the container. max-width: 100% makes the image shrink to fit inside its container.

    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