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

Responsive Page using Grid

accessibility, bem
Aram Nayebbandi•510
@devaramnye
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello there,

worked first time with grid as I was a little scared to start with something new. I like the workflow and the usage of two axis. I can improve more by using repeat() for my templates but I am free for suggestions for my current project.

I worked with ACCESSIBILITY & BEM

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohammad-Moneer•120
    @Mohammad-Moneer
    Posted 8 months ago

    Hello there,

    Great work on your solution! I particularly appreciated your use of the <hgroup> element to group the subheading and heading (<h1>). This is a thoughtful choice that enhances the structure and semantics of the HTML in this context.

    Here are a few suggestions to further improve your code:

    1. Accessibility Enhancements:
      I noticed that the alt attributes for the icon images are currently left empty. Providing a brief description for each icon would improve accessibility, allowing screen readers to convey meaningful information to visually impaired users. For example, you could use descriptions like "Supervisor Icon," "Team Builder Icon," etc.

    2. Refactoring Repeated Styles:
      There are some repeated CSS styles for card headings and paragraphs, such as color and font size. To simplify your code and make it more maintainable, consider consolidating these styles into shared classes. For instance, instead of defining individual classes like .firstcard__h--color, .secondcard__h--color, etc., you could use a single class, .card__h--color, and apply it to all cards. This would look something like:

      .card__h--color { color: var(--very-dark-blue); }
      .card__h--size { font-size: 1.1rem; }
      .card__p--color { color: var(--grayish-blue); }
      .card__p--size { font-size: 0.8rem; }
      

      This approach keeps your code cleaner and easier to modify in the future.

    Overall, your solution demonstrates clear attention to detail and effective use of semantic HTML elements. Well done! I hope you find these suggestions 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
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