Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

3 Column Card Challenge. with HTML SCSS

Joaquin Developer•20
@JoaquinDeveloper
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 frontend mentor community 🤗, this is my second challenge here! any feedbacks are welcome.

have a great day! 😚

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ken•4,915
    @kens-visuals
    Posted almost 4 years ago

    Hey @JoaquinDeveloper 👋🏻

    I have some suggestion to help you fix the accessibility, HTML and some other issues.

    • I'd suggest replacing <section>s with <div>s, because when you use <section> you have to have a heading in it. Besides that <section> is for bigger things in a layout, such as, about us section, contact us, gallery, etc. Don't forget to generate a new report once you fix the issues.
    • For the car icons, add aria-hidden="true”, because they are for decoration only. You can read more about aria-hidden here.
    • When it comes to :hover states, you can apply them directly to the class, instead of :nth-child, and in this case when you have to use different background colors use can use modifier classes to help you. If you're familiar with BEM naming convention than you know what I mean by modifier, if not check out this link.
    • For the mobile viewport width, I suggest reducing width of .card-info to 90% and adding margin-top of buttons to 100px, so you don't have too much white space at the bottom.

    I hope this was helpful 👨🏻‍💻 congrats on finishing the second project, well done. Cheers 👾

    Marked as helpful
  • Joaquin Developer•20
    @JoaquinDeveloper
    Posted almost 4 years ago

    hey @kens_visuals 🖐🏻 , first of all thanks for taking the time to look at my work, I didn't know anything about the aria-hidden so thanks for that im implement in the future. 😋 about <section> tag I wasn't sure how to use but with your comment I have it clear. 😁

    Cheers 🙋🏻‍♂️

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