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

Responsive Testimonials grid using only 1 grid container

accessibility
Mohamed Abdessamed•140
@Brivan-26
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I really enjoyed solving this challenge where I applied the grid system, I used only 1 grid container, and I displayed sub-cards using the great command: grid-template-areas. I'm wondering if you could use breakpoints under 750px because I used 960px(under this view, the cards will be adjoining Your comments and criticisms are welcome

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    David Turner•4,130
    @brodiewebdt
    Posted over 3 years ago

    You will find that you have to adjust break-points to the layout you are working on. You may only use one or you may need more than one. You may have to use a break-point just to fix one small section of a site.

    Wrap your container div in a Main tag and change the attribution div to a footer and it will clear most of the accessibility warnings. There is no H1 on the page, but there doesn't seem to be a logical place to use one.

    Download AXE DevTools and you can clear accessibility warnings while you code. https://www.deque.com/axe/devtools/

    Hope this helps.

  • Alex•660
    @al3xback
    Posted over 3 years ago

    Hi Brivan,

    I think it is better to set grid-template-columns by using fraction unit (1fr). currently the grid items dont fully cover the grid container, leaving minus 1% on the right side.

  • Favour Christopher•90
    @phaevourkhris
    Posted over 3 years ago

    Hi @Brivan-26 you did a great job. And yea, I think you can use breakpoint under 750px, it all depends on what you want to do at those breakpoints.

    Also, see if you can fix the accessibility issues indicated in the report.

    Goodluck

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

Oops! 😬

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

Log in with GitHub