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

3 column preview cards - html and css only

Joanna Skrzypczak•510
@joaskr
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 community, another challenge done :) I had a lot of fun coding it using just HTML and CSS. I didn't ecounter any problems while working on it and I finished it quite fast.

What did you find difficult while building the project?

Since there wasn't any main header on the website I wonder what to do to avoid accessibility issue due to lack of <h1>. I stumbled upon this Stack Overflow discussion and decided to include <h1> in my code but hide it visually.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,890
    @AdrianoEscarabote
    Posted over 2 years ago

    Hello Joanna Skrzypczak, how are you? I truly loved your project's outcome, however I have some advice that I hope you'll find useful:

    I noticed that you used a button in which case the best option would be an a, because in my head when a person clicks on a button written Learn More, he is not confirming a form, or something like, it will be redirected to another page, to Learn More about!

    to solve this problem do this:

    <a href="/" class="suv-btn">Learn More</a>

    I noticed that in higher resolutions the content is stretching a lot, to solve this we can do the following:

    @media only screen and (min-width: 1350px)
    main {
        max-width: 910px;
    }
    

    The remainder is excellent.

    I hope it's useful. 👍

    Marked as helpful
  • 👾 Ekaterine Mitagvaria 👾•7,860
    @catherineisonline
    Posted over 2 years ago

    Sometimes what I do is I add h1, refresh the report and then remove it from my code once it's all good. Some projects do have a such design that you don't need some things but for the sake of the report, you can change it temporarily. I would also add some hover transitions for the buttons, looks much more pleasing. 😊

    Marked as helpful
  • Sinisa Vukmirovic•1,680
    @SinisaVukmirovic
    Posted over 2 years ago

    Hello!

    About your dilema when some of these challenges don't have a header. I think you are right, I do the same. Have a header with a "hidden" <h1> tag in it. I remember watching some tutorial where it was explained to always have an H1, so that the screen readers can see it, and then hide it if it is not needed to be visible on the page.

  • khalid sabbah•110
    @khalid-sabbah
    Posted over 2 years ago

    great job

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub