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

QR Code Component Main using HTML and CSS

accessibility
Ayrton Bolaños•30
@nosquodev
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How would you optimize this code? What would you change about this code? What best practices would you have implemented?


¿Cómo optimizarías este código? ¿Qué cambiarías de este código? ¿Qué mejores prácticas hubieras implementado?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • samaelWebDev•240
    @samaelwebdev
    Posted over 2 years ago

    Hola,

    Algo que yo en lo personal cambiaría sería lo siguiente:

    actualiza el “README” file y agrega tu propio contenido, facilitará la navegación de tus proyectos para las personas que visiten tus repositorios.

    Crea un folder con nombre “CSS” y dentro de ese folder crea tu stylesheet, esto como mejor práctica ya que en un futuro probablemente uses más de un stylesheet.

    Procura usar unidades como REM en lugar de pixels y esto ayudará a la hora de hacer tu proyecto “responsive”

    También procura utilizar Max-width, Max-height en lugar de width y height y esto ayudará también en cuanto a hacer tu proyecto “responsive”

    Excellente diseñó, suerte y feliz coding.

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

    Hi, Ayrton Bolaños! 👋

    Nice work on getting the HTML correct! It's rare to see people coming up with a good HTML structure for this challenge. 👍

    The QR code needs an alternative text because it is the main content of the page. Make sure you describe the purpose of the QR code. Don't include the word "image" on it since the <img> element has already the image semantic meaning.

    I hope this helps. Keep up the good work! 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

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