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

QR code component

accessibility, fresh, pure-css, web-components, less
Favour Hesed Abaye•30
@FavourAbaye
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?

I'm most proud of creating a functional QR code component purely using CSS and HTML, how I was able to handle the challenge, making it responsive. In the future, I would focus on improving the responsiveness and accessibility of the QR code component.

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

Challenge: Ensuring that the elements aligned correctly, maintained consistent spacing, and captured the essence of a real QR code was a challenge.

Solution: I did multiple iterations of adjusting the borders and spacing to make it look visually accurate.

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

I would like help with media queries or other CSS techniques to scale the QR code appropriately. Also, on making the CSS flexbox layout responsive, particularly how to adjust the QR code’s size without distorting its pattern.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pelumi Aiyebola•80
    @Pelumi72
    Posted 7 months ago

    I think the height added to the Qr-code image isn't really necessary or it can be adjusted to look like the original design but every other thing from my point of view is good. It is also a good use of bootstrap. I think for scaling it is best to use percentages because with pixels the images might be static, so it might not be responsive to the change in screen width but with percentages, the image becomes more responsive to the difference in screen-width.

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