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

[🎄] Fylo Dark Theme

accessibility
Kayloâ€ĸ270
@KayloPortal
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


[🎄]

[🔰] Responsive

  • Range 208px+
  • Mobile 375px Desktop 800px+

[🌎] With

  • Regex for validation
  • No libraries and queries, all styled with CSS
  • Semantic HTML5 markups and accessibility

[💖] I will be very happy to read your feedback!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • đŸĻŠ[Shadow]đŸĻŠâ€ĸ420
    @Shadow-IO-oI
    Posted about 2 years ago

    Hello, @KayloPortal!

    First of all, I want to say that your code is very well-written, clear, and responsive. I really like it đŸĻŠđŸ‘.

    I have a few suggestions that might help improve the look of your site. At a width of 800px, there is still enough space to set the benefit row and feed row to 2 columns. Then, at 600px, you could set them to one column.

    Additionally, the footer looks quite big. Perhaps you could consider setting the footer-links to three columns instead of one. On mobile devices, you could set it to two navigation columns and one social-links row.

    Finally, I noticed that there are no hover effects on the address link, phone number, and email link. Maybe underlining or changing the color to white would look nice.

    I hope these suggestions are helpful for you. đŸĻŠ

    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