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

Responsive Product Card with Price and Add-to-Cart Button

accessibility
AHAMED NAJAH•220
@najahaja
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 are you most proud of, and what would you do differently next time?

I'm most proud of implementing a responsive design that adapts well across different devices and using the picture element for optimized image loading. The clean and structured CSS enhances the component's functionality and appearance. Next time, I would focus on improving accessibility by ensuring better color contrast and keyboard navigation, optimizing performance further with techniques like lazy loading, and conducting more extensive cross-browser testing to catch any inconsistencies. Additionally, exploring advanced features to enrich user interaction could enhance the overall project.

What challenges did you encounter, and how did you overcome them?

One challenge I encountered was ensuring that images displayed correctly across different screen sizes, especially for desktop displays with varying heights and widths. To address this, I used the picture element with source tags to provide different images for desktop and mobile views. This approach allowed me to specify different image sizes for various screen resolutions, ensuring optimal visual quality and performance. Additionally, I adjusted the width and height properties in CSS to ensure the layout adapts smoothly, enhancing the overall responsiveness of the design.

What specific areas of your project would you like help with?

I’d appreciate help with a few specific areas of my project. First, I’m looking for advice on optimizing the picture element and source tags to handle responsive images effectively across different desktop resolutions. I also need guidance on ensuring cross-browser compatibility to address any rendering issues in browsers like Chrome, Firefox, and Safari. Additionally, suggestions for enhancing accessibility, such as improving color contrast and making interactive elements fully keyboard-navigable, would be valuable. I’m also interested in strategies for further performance optimization, including minimizing CSS and JavaScript and implementing image lazy loading. Lastly, any tips on managing CSS specificity and improving the organization of my styles for better maintainability would be helpful.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • MATTA RAJESH•100
    @mattarajesh
    Posted 12 months ago

    the page is good in css use disply: flex and flex-direction: coloum then image and content side by side

    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