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

A QR-Code Using HTML and CSS

Owolabi Muktar•20
@CallmeMukty
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Owolabi Muktar•20
    @CallmeMukty
    Posted over 2 years ago

    Hi Vanza, thanks for taking time to review the code some of the corrections have been made but, I'm finding it hard to understand how I can apply the ARIA landmark in this particular project. Then I also find the correction you pointed out on padding a bit confusing. Please help review, thank you.

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 2 years ago

    Hello, Owolabi! 👋

    Congratulations on finishing this challenge! 👏

    First, I recommend formatting the code. I suggest using Prettier. Formatted code helps people to read and understand your code.

    I have some feedback on this solution.

    • The QR code is the main content of the website. It should have alternative text to make it gets pronounced by screen readers.
    • Make the first paragraph a h1. Keep in mind that every page must have one h1.
    • Remove overflow-y: hidden; from the body element. On mobile landscape view where the card needs more than the viewport height of the screen, the users can't scroll.
    • Set padding on the card element to prevent the content from touching the corner of the card. Then, remove the horizontal padding or margin from the elements inside the card.

    I hope this helps!

    P.S. I saw your tweet and you were asking for feedback. Next time, I recommend asking for feedback here by adding specific questions to the "Questions for the community" textarea. Or tells about the part that you struggle. This will give your solution higher chance to get feedback.

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