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

3-column preview card component | Mobile First | CSS Flexbox

accessibility
Mayank Arora•430
@mayankdrvr
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi Frontendmentor community,

This is my 3-column preview card component beginner challenge solution and my second submission. I request the community to review and give feedback for the live site and the shared source code on the following parameters-

  1. Does it follow all the good web accessibility practices?
  2. Is the site mobile first and responsive on all devices?
  3. Do all the padding, margin and border settings comply with the original design?
  4. Are all the colors and font settings matching the original design?
  5. Do you have any other code refactoring suggestion?

Please feel free and do not hesitate to review my code and do give feedback for improvement. All suggestions are welcome. Waiting to learn from your feedback and experience. Thank you for reviewing my challenge submission.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted over 1 year ago

    Hey there! 👋 Here are some suggestions to help improve your code:

    1. No.
    2. No. From 370px - 460px, everything is squished.
    3. No. You are using padding-bottom for texts when you should be using margin instead.
    • Remove all the article you have added to your code; they are not being used correctly. In order to use the article element, the content has to make sense on its own and has to be independently distributable (the content can be placed on ANY site and still make sense).
    • The icons in this challenge are purely decorative which means that their alt tag should be left blank (alt="") to tell screenreader that is should be ignored.
    • The h1 heading is only allowed to be used once per page. In your content it is being used multiple times.
    • To properly center your content to your page, you will want to add the following to your body (this method uses CSS Grid):
    body {
        min-height: 100vh;
        display: grid;
        place-content: center;
    }
    
    • In modern Web Development, all content is built mobile first, in which you style for small screen first and use media-query to style for larger screens. This will ensure that performance and responsiveness are prioritized.

    If you have any questions or need further clarification, feel free to reach out to me.

    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
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