Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Responsive QR-Code page

Eman-Mohamed•100
@emanmohamedsr
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?
Responsive QR-code page.
  • What have I used?
- HTML
- CSS

live Site

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Miguel N Saleme•80
    @MiguelN794
    Posted 9 months ago

    Sure, here is the feedback:

    1. Semantic HTML:

      • The HTML structure is mostly semantic. The use of <main>, <div>, <h1>, <p>, and <footer> tags is appropriate. However, consider using a <section> tag instead of a <div> for the container to enhance semantic meaning.
    2. Accessibility:

      • The alt attribute for the image is well-used, providing a description for screen readers.
      • To improve accessibility, consider adding aria-label attributes where necessary, such as on the links in the footer to describe their purpose.
      • Ensure that the color contrast between text and background is sufficient for readability.
    3. Responsive Layout:

      • The current HTML does not include any responsive design elements. Ensure that the CSS includes media queries to handle different screen sizes.
      • Use relative units (like percentages or viewport units) instead of fixed units (like pixels) for widths and heights to make the layout more flexible.
    4. Code Structure, Readability, and Reusability:

      • The code is well-structured and readable. The indentation and spacing are consistent.
      • Consider using classes or IDs to target specific elements for styling or JavaScript functionality, which can improve reusability.
    5. Design Consistency:

      • Without the design reference, it's hard to determine if the solution differs considerably from the design. Ensure that the CSS matches the design specifications provided by Frontend Mentor.

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