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

Responsive Qr code scanner psge using css ,html5

accessibility
Subodh Kushwaha•10
@subodh1221
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I found very difficult to center the image of Qr and its takes a lot of time to know that how to manage its border radius.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Manuel Lucero•140
    @MalexLucero
    Posted almost 3 years ago

    Enclosing the image, title, and text into an article or div element will help. You can then center the article/div element without worrying about the image.

    <article>
        <img src="yourImg.jpg" />
        <h1>card title</h1>
        <p>card text</p>
    </article>
    

    In the CSS, you could position the article element in the center by adding flex box to the body.

    body {
        display: flex;
        flex-direction: column;
        justify-content: center;
       align-items: center;
    }
    

    css-tricks.com/snippets/css/a-guide-to-flexbox/ Here's my favorite guide on flexbox. :)

    Keep it up!

  • Wasswa Enock Male•50
    @wasswaenockmale
    Posted almost 3 years ago

    Try working on your width for the element you gave a background-color of white, then the rest will work very well. And you also need to focus on the giving a border radius to the qr-image. Then lastly and most importantly, try following the style guide, It will guide you on which font weights to use, font-family to use and background-colors to focus on in that particular project. Other congratulations for the zeal of wanting to focus on frontend

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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