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

Responsive landing page using Grid

bem, accessibility
Manuel Fernando Gallego Arias•120
@mgallegoa
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jairo Valderrama•420
    @jairovg
    Posted almost 3 years ago

    Hey @mgallegoa, here are some feedback on your solution

    • You're using for background-size a contain value which stretches the image to its container height, but it won't do it to its width. Try to check the dev tools for different breakpoints like 425px or 768px and see how this value affects the page. Look for the possible values you may use in the MDN docs.
    • You have multiple a11y issues; probably solving one, in particular, may solve others; this is page must have one main landmark. You can read more about this issue on the Deque University Axe rules page.
    • The navigation elements are a list with a hover state but are not interactive elements. So I suggest you add an anchor element inside each li and handle the different element's states here.
    • The same comment above applies to the logo and all the page elements where you handle the hover state with non-interactive elements.
    • You have a ul wrapped by a div in the footer. Think about these elements and what would be the better semantic way to handle them.
    • I've noticed you also are using some empty div elements with the goal of handling background images with images at different breakpoints. Think if all these images are decorative or if some of them are content images. Here I'm sharing an entry about handling responsive images with HTML elements, in case not all are decorative or need to be addressed, not as background-images.
    • Finally, I think client testimonials may be considered a list. If you see the documentation, list allows having flow content elements.
    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
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