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

3 Column Preview Card Component Main

imen dhaoui•130
@imendh02
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


Please Provide Feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted over 3 years ago

    Hello @imendh02 , I have some suggestions:

    To get rid of the accessibility issues :

    • Document should have one main landmark. Wrap the body content in< main>tag read more about main landmark.

    • You don't need div's ,<main >can wrap all the component (the three cards) .

    • Use a <footer> for the class="attribution".

    • You can add a <h1> with class="sr-only"(Hidden visually, but present for assistive tech).

    .sr-only {
    	border: 0 !important;
    	clip: rect(1px, 1px, 1px, 1px) !important; /* 1 */
    	-webkit-clip-path: inset(50%) !important;
    		clip-path: inset(50%) !important;  /* 2 */
    	height: 1px !important;
    	margin: -1px !important;
    	overflow: hidden !important;
    	padding: 0 !important;
    	position: absolute !important;
    	width: 1px !important;
    	white-space: nowrap !important;            /* 3 */
    } 
    

    To read more This fairly modern technique will hide or clip content that does not fit into a 1-pixel visible area. Like off-screen content, it will be visually hidden but still readable by modern screen readers.

    • You can replace the <h1 > by <h2>.

    • Images must have alt text. In this challenge all the images are decorative, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images.

    • Swap the buttons for anchor tags. Clicking those "learn more" buttons would trigger navigation not do an action so button elements would not be right.

    • If you are using a button element, always tell the browser the type of the button to prevent the browser from submitting any information. In this case, it should be a type="button".

    • A hover effect that raises a button looks strange. It's not a natural movement to happen.

    CSS:

    • <main> shouldn't have position: absolute; , It's a flex container.

    • You should use em and rem units .Both em and rem are flexible, scalable units which are translated by the browser into pixel values, depending on the font size settings in your design. Using px won't allow the user to control the font size based on their needs.

    • For each card :

    {
    display:flex;
    flex-direction: column;
    align-items: flex-start;
    }
    
    • Set everything inside the cards to have some margin in one direction. Only the button wouldn't need it , margin-top: auto; for the <a>Because this is a flex column, margin-top: auto will push it to the bottom of the cards.

    • border-radius and overflow hidden to the container <main> that wraps all the cards so you don't have to set it to individual corners.

    • 375px is very late to start the mobile layout. Start it as soon as there is room for the layout.

    Hopefully this feedback helps.

    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

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