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

I use some resource with google search

mahdigithubr•20
@mahdigithubr
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?

The challenge is very interesting

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

very easy

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

amazing

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,890
    @AdrianoEscarabote
    Posted 10 months ago

    Hi mahdigithubr, how’s everything? I think your project turned out great! However, I have some feedback that I think might be useful:

    Since this project is only based on a single page component, there is no need for a h1 tag. It's always a good idea to prevent accessibility errors, so I believe it would be beneficial for you to add a "h1" in this component. Don't worry if you forget about "h1," though; it's a good practice for when you are developing larger sites.

    <h1>Improve your front-end skills by building projects</h1>
    

    images must have alt text unless it is a decorative image, for any decorative image each IMG tag must have empty alt="" and add aria-hidden="true" attributes to make all the assistive technologies of the Web, as screen reader.

    Learn the differences between decorative/meaningless images vs important content.

    The rest is amazing.

    I hope this is helpful. 👍

  • P
    adhSwede•80
    @adhSwede
    Posted 10 months ago

    Pros:

    • Code format is nice and readable
    • Nailed the dimensions.
    • Colors are on point.
    • End result is pretty spot on (only downside is the attribution tag pushing everything up a bit)

    Cons (Not really in your case, just a few heads up):

    • I would use an H1 instead of an H4 for semantics, since it is the main heading on the page.
    • Could do with a bit less divs and a little more semantic tags. e.g. <main> <footer>

    Summary: All in all Amazingly done on the styles, the use semantics and the use of H1 are the only things i would improve here.

    Bonus tip: For my attribution tags I've went with an absolute position about 2 rem from the bottom, it takes the element out of the normal flow and in your case it would have made your solution 1:1 with the design since you were already good on the dimensions.

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