Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive QR code component

accessibility
Revadi Sundaram•90
@RevadiSundaram
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedback are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bishal Singh Deo🎮•1,420
    @Bishalsnghd07
    Posted over 1 year ago

    Hi, @RevadiSundaram

    Good to see you on completing this challenge👏

    Your project looks really amazing🎉

    I have some suggestion about your code that might interest you.

    • There is an very useful browser extension called Perfect Pixel that allow you compare with the design image and that gives the exact dimensions to make your web page pixel perfect. I recommend it to you.

    • Use min-height of 100vh instead of height to the body element. Using height in your body, it will only break your layout, never ever use height in main landmark or in body of your layout, it gives disaster solution. You can use inside main component, if needed.

    body { height: 100vh;❌ min-height: 100vh;✅ rest same }

    I hope this suggestion is useful for future projects.

    Once again Welcome to Frontend Mentor Journey❤️

  • Fernando Batista•630
    @FernJBatista
    Posted over 1 year ago

    The end result looks really good!

    I would recommend you some things though.

    • Try to use an organized heading structure, you used an h4 here for the title, but it would be better to use an h1 and style it as you need.

    • Look up text size guides, in this case the text could be a bit small (I know, I know, one pixel is a bit too naggy). I think a good starting point is that paragraph texts are usually 16px or 1rem, from there you can also give your headings bigger size depending on their hierarchy.

    Other than that you did great!

    Happy coding, keep it up!

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