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

HTML, CSS, CSS Variables and Flexbox and Grid

P
David Turner•4,130
@brodiewebdt
A solution to the Equalizer landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is one of the first times I used CSS Grid to any extent. There are still some things I would like to improve. Any feedback would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, awesome work on this one. Desktop layout look really great, you could make the upper-right-corner background to be a bit bigger. The mobile state looks great as well but if you go to at 390px below, the screen starts to hide the content and creates a horizontal scrollbar.

    Here are some other suggestions for the site:

    • For the site-logo, remove the word logo from it since you don't want to include words that relates to graphic such as logo when using alt attribute.
    • On the phone-section, the pattern background-image is only decorative so use the alt="" on it. Usually, when you use aria-hidden="true" on an img , you use an empty value for the alt attribute.
    • For the phone image, I think you can add a descriptive alt value for it , it could be something like alt="equalizer app running on mobile".

    FOOTER

    • Same as well for the site-logo, remove the logo word from it.
    • For the social-media links, remove the word link from each of the a tag since screen-reader will already announce that it is a link, so use only the social-media's name on it.
    • Adding an extra aria-hidden="true" on the img tag for each social media so that it will be totally ignored by screen-reader.

    Aside from those, great job again on this one.

    Marked as helpful
  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! David, really impressive and really good designed and it's responsive too. I checked your code and you really structured your code really well.

    Keep it up! ❤️

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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