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

Fylo landing page with two column layout using pure CSS.

Rohit•330
@Rohitgour03
A solution to the Fylo landing page with two column layout challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Here is my solution to this Challenge, Please have a look. Your little suggestion or tip can help me improve as a newbie in the front-end.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Dave•5,295
    @dwhenson
    Posted over 3 years ago

    Hey @Rohitgour03 - nice job here!! 👍

    Here's a few small comments for you to consider:

    1. I'd add curser: pointer to your buttons - this seems to be a common convention and what most people expect.

    2. Do you have a label associated with your input elements? You should have, but the FEM accessibility linter isn't picking it up as an error. Here's a nice article that gives a good explanation of why this is: https://css-tricks.com/html-inputs-and-labels-a-love-story/ (you can always hide the label using CSS if you don't want people to see it)

    3. I noted that you sent outline: none on everything. If you remove outline styles then it is important to add back in your own custom outline styles as otherwise it can make it very hard for keyboard users to navigate the page.

    If you don’t like the default styles I have found the advice in this article very useful, and use it in pretty much all my projects: https://css-tricks.com/the-focus-visible-trick/

    Here's the code I usually add:

    /* Add styled focus states on tab not hover */
    
    :focus-visible {
      outline: 3px dotted currentColor;
      outline-offset: 0.25rem;
    }
    
    :focus:not(:focus-visible) {
      outline: transparent;
    }
    
    1. Lastly, I think the links in your social icons also need an accessible name - if you don't want to add text adding aria-label: Facebook or whatever to the link itself should solve this problem and get rid of those errors.

    2. Lastly I noted the logo in the footer's color wasn't changing. To do this you either need to inline the svg and change the fill setting, or make a copy of the file and change the fill setting. I find svgs super tricky, so this might not work but it's what I would try!

    Great work and keep going!!

    Cheers 👋

    Dave

    Marked as helpful
  • MichalTrubini•1,220
    @MichalTrubini
    Posted over 3 years ago

    Hello there,

    I suggest using this tool to change color of svg files. It works perfectly.

    https://codepen.io/sosuke/pen/Pjoqqp

    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

Oops! 😬

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

Log in with GitHub