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

QRCode component with React and ChakraUI

react, chakra-ui
Caio Bukvar•50
@caiobukvar
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first frontendmentor task! Anything to share about it?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • EthanAmato•130
    @EthanAmato
    Posted over 2 years ago

    Hey there! First of all I want to say fantastic job! It looks beautiful and I love the incorporation of React and ChakraUI. If you want to address some of the warnings that the accessibility report gave you, check out the following:

    1. "Document should have one main landmark"
    • Essentially, it's telling you to make use of semantic HTML (documentation here) to make the site easier to read for screen readers. Essentially, replace the <div className="container"> with a <main/> tag.

    2 "Page should contain a level-one heading"

    • I believe this error is coming from a lack of an H1 tag in your code. According to the ChakraUI documentation, this can be accomplished with the <Heading as='h1'/> component

    3 All page content should be contained by landmarks

    • I think this is coming from how react renders jsx and isn't too much cause for concern. Here is a stack overflow post regarding it: link

    Overall, fantastic job and I hope you continue your journey :)

    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