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

3-column-preview, Html, Css, Responsive Layout

accessibility
Neha Nalini Kennedy•100
@nehanalinik
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


Any feadback would be much appericiated! 🤠

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,675
    @FluffyKas
    Posted over 3 years ago

    Hey there,

    Your solution looks really good! All screen sizes seem to work well, I'd just like to discuss a few bits of your code.

    1. The height on your "main__container": try removing it and see what happens. :) Not much, right? Setting height is usually not necessary (there are exceptions, of course). Your elements have their own default height which you can increase by giving them a padding.

    2. Setting 200vh height on the body might be a bit too much? A min-height: 100vh is usually enough (plus some margin-top and -bottom if you'd like).

    3. You use width and max-width and you give them the same values which doesn't make a lot of sense. width: 400px will set a fixed width on your component so max-width then don't do much for responsiveness if given the same value. What you could do instead is something like this: width: 90%, max-width: 400px. Or, if you'd like to make it even shorter: width: min(90%, 400px). Adding min means the smaller of the 2 values will be chosen and applied to your component automatically so it's exactly the same as the previous example, just in one line. Try this out, see the difference it makes :)

    4. You should leave alt texts empty in this challenge, as they're really just decorative. You could give them an aria-hidden= true to make sure the screen reader skips them.

    I hope these tips will help you a bit in the future. All in all, your solution is still great! ^^

    Marked as helpful
  • Alex Nix•170
    @AlexNixx
    Posted over 3 years ago

    Hi! Great job, i really like it. After code review i wanna to say, if u have 3 same column use one class to compose it, and add a second class to style it.

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