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

QR code component using responsive design

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

Solution retrospective


Feedback always appreciated. Used pixels to follow given design as opposed to rem and em units.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted over 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    HTML 🏷️:

    • This solution generates accessibility error reports, "All page content should be contained by landmarks" is due to non-semantic markup, which lack landmark for a webpage

    • So fix it by replacing the <section class="card-section"> element with the semantic element <main> along with wrapping the <p> element with <footer> element in your index.html file to improve accessibility and organization of your page.

    • What is meant by landmark ?, They used to define major sections of your page instead of relying on generic elements like <div> or <span>

    • They convey the structure of your page. For example, the <main> element should include all content directly related to the page's main idea, so there should only be one per page

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • Adriano•330
    @adriano-wb
    Posted over 2 years ago

    Aqui estão algumas sugestões para melhorar este código:

    1. Adicione uma descrição ao elemento de imagem: Adicione um atributo "alt" descritivo para a imagem para melhorar a acessibilidade e fornecer informações úteis para os usuários que usam leitores de tela.

    2. Remova pré-conexões redundantes: As pré-conexões para o mesmo recurso não são necessárias, portanto, você pode remover a segunda pré-conexão do Google Fonts.

    3. Agrupe as pré-conexões: Agrupe as pré-conexões relacionadas para melhorar a legibilidade e o desempenho do código.

    4. Use uma classe mais descritiva: Em vez de usar "card-container", use uma classe mais descritiva para identificar o elemento, como "qr-code-container".

    5. Adicione um estilo de plano de fundo: Adicione um estilo de plano de fundo ao elemento body ou ao elemento principal para melhorar a aparência do site.

    6. Use espaços entre os atributos: Adicione espaços entre os atributos para melhorar a legibilidade e a facilidade de leitura do código HTML.

    7. Considere usar um pré-processador CSS: Considere usar um pré-processador CSS como o Sass para simplificar o processo de escrita de CSS e melhorar a manutenibilidade do código.

    8. Adicione comentários descritivos: Adicione comentários descritivos ao código para ajudar a entender o que cada seção do código faz.

    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