Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Testimonial Page Using Cube CSS

accessibility, cube-css
MarkPraise•150
@MarkPraise
A solution to the Testimonials grid section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What specific areas of your project would you like help with?

I really need a feedback concerning the responsive behaviour of the page. It seems there are some anomally i cant get my head around. The site streteches as the desktopsize decreases. I want it centered. I will be very grateful if a positive feedback is given Me.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    Why have you put tabindex all over this??? That is a serious accessibility failure. You need to remove them all.

    I recommend you change a lot of the html actually.

    • remove all the headers (multiple headers can cause a lot of confusion about content structure) -- change all the h1s to h2s. Each page should only ever have one h1. If this was on a real full web page the h1 would be higher up the page.
    • I recommend using the figure element for each testimonial card instead of articles. This would allow you to use figcaption for the name, image and verified text.
    • the testimonial paragraphs should be inside a blockquote.
    • it's better for performance to keep the css reset at the start of the styles instead of linking a whole separate css file
    • don't remove outline and use border for focus. You only need to use focus-visible for interactive elements and it is much better to stick with outline to avoid layout shift. There are no interactive elements in this design though so you don't actually need to style focus visible at all.
    • the grid should have a max width in rem not a width in %
    • the grids margin should be small. Remember phone screens can be 320px wide. This content is very narrow at the moment.
    • don't use complex css selectors if you can help it. High specificity css is a nightmare to manage on larger projects. Use single class selectors whenever possible.
    • class names are written without capitalisation. It's not a problem but this is a heavily established convention.
    • the quote image is overlapping text. Use z-index.
    • media queries must be defined in rem or em not px. https://fedmentor.dev/posts/responsive-meaning/

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub