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

Responsive Website Using CSS Grid And Flex

Adem Baccara•130
@Adembc
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please provide feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. The layout both desktop and mobile is good and the responsiveness as well.

    Some suggestions would be:

    • The company logo's alt text should have been alt="Fylo" since the logo itself have that word, better to use it in the alt. Also, when using alt attribute, do not include words like "icon" "image" "logo" or anything else that relates to "graphic", assistive tech will handle those for you.
    • The company logo in the header as well, since you are adding an interaction with it, better to nest it inside a tag, along with an aria-label="homepage", since mostly company logo links to the homepage.
    • Have a main element that wraps the whole main content. This will clear up the issue in your report as well as adding more to the structure of your website.
    • Do not skip a heading level. Use heading tags incrementally by one. If you use h1 make sure to have h2 before you use h3. On your solution, you didn't use h3 but you used h4 and h5.
    • The alt text for the person in the testimonial could have used their name as the value, like alt="Satish Patel".
    • Only use 1 h1 per page. You use the 1st h1 on the hero-section, the 2nd one is at the cta-section.
    • On the submit button in the form, it would be better to use button type="submit", the reason is that, you could add a more descriptive information about what that button does, you could add aria-label="submit form" on the button instead of just get started for free which doesn't really describe what it does right.
    • Company logo in the footer could have used alt="fylo" as well.
    • The links on the footer could have used ul as well, since those are list of links.
    • The a tag that holds the social media icons should have an aria-label, like aria-label="facebook" for the a tag that wraps the facebook icon. This will ensure that screen reader users knows where this link should go.

    Aside from those, great work.

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

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