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

sass htlm5 css3 grid flexbox res

sass/scss
kappaβ€’180
@kappa20
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


responsive without using media query instead i mobile first approach and max-width and min-width to prevent the card container from expanding

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dev Rathoreβ€’2,540
    @GitHub-dev12345
    Posted over 3 years ago

    If you want to reduce your accessibility, Change this code. 😊

    <div class="container"> to <main> ( Used main tag for main card design ) <div class="attribution"> to <footer> ( Used footer tag for footer design)

    I hope you find this helpful

  • Dev Rathoreβ€’2,540
    @GitHub-dev12345
    Posted over 3 years ago

    Congratulations πŸ‘πŸ‘πŸŽ‰πŸŽ‰πŸŽ‰ to complete your challenges. I suggest you in your card design to give border-radius: 13px. I hope you find this helpful

  • Jβ€’1,020
    @jrmy-dev
    Posted over 3 years ago

    Hi! Well done!

    If this can help, I have a suggestion:

    • Fix accessibility issues: to do so, change your <h3> to <h1>. For the landmark issue, change <div class="container"> to <main> and change your <div class="attribution"> to <footer>

    If you have any questions feel free to ask, I'll try my best to help and answer! πŸ™‚

  • kappaβ€’180
    @kappa20
    Posted over 3 years ago

    Thank you <3

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

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