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

Qr code component whith html and css + flexbox

weydsonlino•30
@weydsonlino
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first project here, and I would like to receive feedback and tips. thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • David Ochoa•270
    @davidochoadev
    Posted about 2 years ago

    The last <div> could also be a <footer>, or alternatively, you could add role="contentinfo" to your div. However, on MDN Web Docs, they always recommend using a <footer>. The use of <footer> is recommended for several reasons when structuring the content of a web page.

    Firstly, a <footer> element provides semantic meaning to the content it wraps. It clearly indicates that the enclosed content represents the footer section of the page, which typically contains information related to the document as a whole, such as copyright notices, contact details, and navigation links.

    By using a <footer>, you improve the accessibility and assistive technology support of your website. Screen readers and other assistive devices can recognize the <footer> element and convey its purpose to users, allowing them to easily navigate and understand the structure of the page.

    Moreover, <footer> helps with search engine optimization (SEO). Search engines analyze the structure and content of a webpage to determine its relevance and rank it in search results. By using semantic elements like <footer>, you provide additional context to search engines, enabling them to better understand and index your content.

    In addition, using a <footer> element makes your HTML code more readable and maintainable. It clearly delineates the footer section, separating it from the rest of the page's content. This separation enhances code organization and makes it easier to modify or update the footer content independently without affecting other sections of the page.

    Overall, incorporating a <footer> element in your webpage structure offers benefits in terms of semantics, accessibility, SEO, and code maintainability. It ensures clear and meaningful presentation of footer-related content while improving the overall user experience.

  • Account deletedPosted about 2 years ago

    Hello Coder 😊

    Your solution is great✨ and congratulations for successfully completing an another newbie challenge🎉

    and there is a small suggestion that might be helpful for you

    QR code image : The alt attribute provides alternative information for an image if a user for some reason cannot view it and screen readers use the alt attribute to convey the message about the image

    And here the qr code image is not for decoration and that's why you need to write an alt attribute value for it

    <img src="images/image-qr-code.png" alt="qr code">
    
    

    Hope that was 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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub