Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

LOOPSTUDIOS LANDING PAGE 🎯 [ ACCESSIBLE - BEM - VANILLA CSS3 ]

accessibility, lighthouse, bem
Abdul Khaliq 🚀•72,380
@0xabdulkhaliq
A solution to the Loopstudios landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👾 Hello, Frontend Mentor Community,

This is my solution for the Loopstudios Landing Page.

  • Scored 98.6% on Google Pagespeed Insights! 🤩
  • Comes with Custom navbar w/ scroll-in & scroll-out animation 🔥
  • Accessible hamburger menu w/ ES6 🍔
  • Actually i delayed to post this solution, this was completed about 5 months ago ⏪
  • Minified the css files to improve site performance 🚀
  • Used Prettier code formatter to ensure unified code format ⚙️
  • Layout was built responsive via mobile first workflow approach 📲
  • Had a lots of fun while building this challenge ! 🤠
  • Feel free to leave any feedback and help me to improve my solution 💡

.

👨‍🔬 Follow me in my journey to finish all junior challenges to explore solutions with custom features and tweaks

Ill be happy to hear any feedback and advice !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Posted over 1 year ago

    Hello there! 👋 The solution you provided five months ago for this challenge looks great! 🌟 However, I have a few suggestions to address some potential drawbacks in terms of accessibility:

    • Firstly, let's talk about the "main__creations" section:

      The elements in that section have a hover effect, making them seem like interactive elements such as buttons or links. Since you're showcasing a list of "creations", and users might expect to navigate to these "creations" by clicking on them, it might be more accessible to implement actual links (<a>) instead of using <div>.

      Now, here are the drawbacks of using <div> instead of a link:

      • Users who rely on keyboard navigation can't easily move through the "creations" using the Tab key.
      • There is no pointer cursor in your solution.
      • Users might expect some action to occur when they click on the items.

      For a more elegant solution, you might want to consider implementing some of the techniques shared on this page: Cards - Inclusive Components 📘.

    • Consider adding a "Skip to main content" link to your solution:

      This helps users bypass header links and directly access the main content, improving the experience for those using screen readers or keyboard navigation.

      You can follow a guide on how to create a "Skip to content" link by visiting the following link: How to Create a "Skip to Content" Link | CSS Tricks 📘..

    • Media Queries and Horizontal Scrollbar:

      Lastly, a horizontal scrollbar appears between 56em (896px) and 1024px due to a single media query and the "OUR CREATIONS" section. You could either add more media queries or use the RAM (Repeat, Auto, Minmax) technique in CSS to avoid the need for multiple media queries.

      You can learn more about the RAM technique here: Repeat, Auto, Minmax | Web.dev📘..

    These suggestions are aimed at enhancing your project's accessibility. Keep up the fantastic work! If you have any questions or need further assistance, feel free to ask. 😊

    Marked as helpful
  • Pratyush•60
    @pra-23845
    Posted over 1 year ago

    can you just tell me how did you make that animated sticky navigation bar i know how to make sticky navbar but not with animation i really like that one and i want to use it

  • Saad Hisham•1,770
    @Saad-Hisham
    Posted over 1 year ago

    Welcome back, bro 🎉😅

  • Lucas 👾•104,160
    @correlucas
    Posted over 1 year ago

    Congrats for the Mentor of the year!

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

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