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

Responsive QR Code Component with Custom CSS Styling and Background.

accessibility, airtable, angular-material, emotion, astro
yuriinyk•150
@yuriinyk
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 proud of how I was able to implement a responsive design using CSS Grid and Flexbox, which ensured the layout looks great on both mobile and desktop screens. Next time, I would focus more on accessibility by adding aria attributes to improve keyboard navigation and screen reader support.

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

The main challenge was ensuring the design adapted correctly across different screen sizes. I overcame this by fine-tuning the media queries and utilizing Flexbox for more flexible and dynamic positioning of elements.

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

I would appreciate feedback on the responsiveness of the components on mobile devices, especially suggestions on improving media queries or other methods for better optimization for various screens. Additionally, any advice on making the gradient stripe background more efficient or improved would be very helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Julia Bush•360
    @juliabush
    Posted 6 months ago

    Avoid using pixels for font size. Instead use rem. You can find pixel to rem converters online, for reference 16px is 1 rem. This is best practice for responsiveness as some users may set there browsers to display larger font size, to help them with readability. That is why rem is so important, as it can adjust to these preferences, whereas pixels are fixed. Hope this tip helps :)

    Marked as helpful
  • MaximYarosh•20
    @MaximYarosh
    Posted 6 months ago

    Does the solution include semantic HTML?

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