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

Responsive QR card

accessibility, bem, vite
Amit Shaw•40
@iamitshaw-1998
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 have make this assignment responsive.

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

Image overflow issue at smaller-screen sizes. Resolved issue by using media query.

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

How to make website responsive?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,820
    @thisisharsh7
    Posted 3 months ago

    Great work, Amit! 👏 You've done a solid job making this QR code component responsive and accessible. Here's some detailed feedback:

    👍 What’s working well:

    • Semantic HTML usage (<figure>, <figcaption>) is well done.
    • The use of CSS custom properties makes color management scalable.
    • Responsive scaling via clamp() is excellent — clean and modern.
    • Accessibility is considered with proper alt and ARIA labels. 👍
    • Good use of a reset.css to maintain cross-browser consistency.

    🔍 Suggestions for improvement:

    • You mentioned the image overflow issue — nice catch! Your use of media queries helped solve it well. You could explore using container queries in the future for more flexibility.
    • Consider adding a subtle box-shadow to the .card to visually elevate it. Use tools like this box-shadow generator for inspiration.
    • Padding inside .card__information could be reduced slightly on mobile for better spacing.
    • You could also explore reducing the vertical margin on .card__information when screen width is small to improve layout flow.

    You asked how to make a website responsive — you're already on the right track! Use relative units (em, rem, %, vw/vh) and media queries. Also consider using flexbox or grid layout with minmax() and auto-fit for dynamic scaling.

    Great job overall! Keep building! 💪🚀

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