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

QR Code challenge by DominikaPap

Dominika Papierska•60
@dominikapap
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


-Did I use any bad practice? -Is using px ok here, or should I have changed them to rem? -What could have been done better?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul•8,560
    @Samadeen
    Posted over 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. . Here are my suggestions 1.You should use <main class="main"> instead of <section class="main">. 2. You should also use the footer tag instead of the <section class="footer"> 3. Its best you add a text to the alt attribute in the img tag

    . Regardless you did amazing.. Happy coding!!!

    Marked as helpful
  • Brian Johnson•210
    @BrianJ-27
    Posted over 3 years ago

    Hey There @dominikapap Great job overall laying out this project. You have this card square in the middle and that is awesome!

    I have a few things to share with you regarding your codebase. I'll just number them for you :)

    1. for your <section class="main"> tag, change the <section> tag to a <main> tag

    2. for your <section class="footer"> tag change the <section> tag to a <footer> tag **Formatting your code this way should remove all of your accessibility & HTML issues with the code

    Regarding best practices, I see you have 2 css stylesheets in the root directory of your project. It is usually best to create a "css folder" then place those 2 stylesheets within that folder. When you do that, you next need to go back to your index.html file and modify your filepath to the stylesheets.

    That's all I see for now at quick glance but great job overall. Happy Coding

    Marked as helpful
  • Rémi Martineau•355
    @MartineauRemi
    Posted over 3 years ago

    Hey Dominika ! Nice work on this solution, congratulations :) Here are some tips :

    • You should read about semantic html: https://www.w3schools.com/html/html5_semantic_elements.asp

    In your case, you could replace <section class="main"> with <main class="main">. Same thing with the <section> wrapping your attribution, at the bottom of your html file. Why not use a <footer> tag instead ? :)

    • if you want to set an empty alt property to an image, I suggest you to add a property called 'aria-hidden' set to true. More on aria-hidden: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-hidden

    For this particular example though, I would put something in the alt property, since the image is not purely decorative, and a description could be helpful for screenreaders users.

    Hope this can help you ! Keep up the good work, and happy coding :)

    Marked as 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

Oops! 😬

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

Log in with GitHub