Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

3-column-preview-card-component

Antonio Casado Valencia•220
@acasadovalencia
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 2 years ago

    Awesome work completing this challenge

    Your solution looks great however with regards to your accessibility issues, your html document should have a main landmark in order to identify the main content of the page. In order to resolve this issue just wrap all the elements within your body element inside a main tag like this.

          <main>
            <section class="cars__section">
              <div class="container">
                <div class="sedans__car">
            <img src="/images/icon-sedans.svg" alt="Sedan car" class="type__img">
            <h1 class="type__name">Sedans</h1>
            <p class="paragraph">Choose a sedan for its affordability and excellent fuel economy. Ideal for cruising in the city 
              or on your next road trip.</p>
            <button class="btn btn-sedan">Learn More</button>
          </div>
          <div class="suv__car">
            <img src="/images/icon-suvs.svg" alt="Suv car" class="type__img">
            <h1 class="type__name">SUVs</h1>
            <p class="paragraph">Take an SUV for its spacious interior, power, and versatility. Perfect for your next family vacation 
              and off-road adventures.</p>
            <button class="btn btn-suv">Learn More</button>
          </div>
          <div class="luxury__car">
            <img src="/images/icon-luxury.svg" alt="Luxury car" class="type__img">
            <h1 class="type__name">Luxury</h1>
            <p class="paragraph">Cruise in the best car brands without the bloated prices. Enjoy the enhanced comfort of a luxury 
              rental and arrive in style.</p>
            <button class="btn btn-luxury">Learn More</button>
          </div>
      </div>
      </section>
    </main>
    

    Note: indentation is inconsistent

    Secondly in order to resolve your second accessibility issue, use <div> instead of <section since it is more meaningful and more descriptive. The section tag becomes purposeful only when the the role attribute is specified.

    Hope this helps

    Cheers

    Marked as helpful
  • Antonio Casado Valencia•220
    @acasadovalencia
    Posted over 2 years ago

    Hello Samuel. Thanks for your feedback! I will try to fix following your comments.

    Thank you again for your support.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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