Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive landing page using display flex

accessibility
pauleenann•240
@pauleenann
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What can I do to improve?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing the Product Preview Card Component challenge! 🎉 This project showcases your ability to create a clean and responsive user interface, a crucial skill in front-end development. Here are some best practices and suggestions to enhance your project:

    • HTML Best Practices:

      1. Semantic HTML: Ensure the use of semantic elements for better accessibility and SEO. For example, consider using <section> for grouping related content and <header> for the top part of your card.
      2. Alt Attributes for Images: Include descriptive alt text for images to improve accessibility for screen readers.
      3. HTML Structure: Your HTML is well-structured, which is great for readability and maintainability.
    • CSS Best Practices:

      1. Responsive Design: Make sure your design is responsive and looks good on different screen sizes. Use media queries effectively to handle layout changes.
      2. Hover and Focus States: Implement distinct hover and focus states for interactive elements like buttons to enhance user experience.
      3. Font Loading: Ensure that the web fonts are loaded efficiently to reduce the page load time.
    • Accessibility Considerations:

      1. Keyboard Navigation: Ensure that all interactive elements are navigable using a keyboard.
      2. Contrast and Color Accessibility: Make sure that text and background colors have enough contrast for readability, especially for users with visual impairments.
    • General Suggestions:

      1. Cross-Browser Testing: Test your page across different browsers to ensure compatibility and a consistent experience.
      2. Performance Optimization: Optimize images and assets to improve load times, especially for mobile users.
      3. Code Validation: Use tools like W3C Validator to ensure your HTML and CSS are error-free and follow best practices.

    You're doing an excellent job in your development journey. Keep up the great work, and continue challenging yourself with new projects to further enhance your skills! 💪

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