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

Static-qr code-component with clean css

ADCByDefault•190
@ADCByDefault
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


i would appreciate if you could find any way to improve my css or html code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Brian Schooler•440
    @superschooler
    Posted almost 3 years ago

    Gread job on this project, it looks fantastic! I love your use of variables in CSS and using rem instead of px for the most part. However, <p> uses px while <h1> uses rem, so if the user has a different default font-size they won't scale the same.

    A couple pieces of constructive criticism are below. They're very nit-picky since you did a very good job, but something to perhaps keep in mind on the next one!

    Additionally, alternate text (alt) is supposed to be a textual description of the image in case the image can't load OR the user is visually impaired and using a screen reader. In your case, I'd change the alternate text from "refresh if you don't see the qr code" to something like "QR code linking to frontendmentor.io".

    Also, to help with accessibility, you might consider trying to use a <main> or <article> tag for the QR code element instead of <div> for everything.

    Marked as helpful
  • Mihailo Dilparic•190
    @TheDilp
    Posted almost 3 years ago

    This is pretty great! Nice work.

    For HTML you can see that you have some accessibility issues, I would recommend adding a <main> tag that wraps the card. Otherwise it looks good to me.

    As far as CSS goes I think that giving the card some box-shadow would improve it and bring it closer to the final design.

    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