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

Scoot Multipage Website 🛵🛵 w/HTML, CSS & JS

jquery, sass/scss, semantic-ui
Koda👹•3,830
@kodan96
A solution to the Scoot multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

50th SOLUTION 🎉🎉

Made with:

  • HTML 🦴
  • SCSS 🖌️
  • JS 🤖
  • mobile-first workflow 📲📲
  • jQuery for shorter JS code 📕
  • used autoprefixer to ensure browser compatibility 🧭🧭
  • minified CSS files for better performance🚀
What challenges did you encounter, and how did you overcome them?

if I see one more SVG....

Read the FAQ-s

What specific areas of your project would you like help with?

if you notice anything, do what you gotta do... 👇👇

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • dewyrag•230
    @dewyrag
    Posted about 1 year ago

    Very nice, can you tell me how you learned JS? I just started the freecodecamp javascript section and its so confusing. all i understand are variables

  • Account deletedPosted about 1 year ago

    @kodan96 Unfortunately, this needs a lot of work.

    • Why did you make your class="header_menutoggle" a div...❓This is meant to be an interactive element and a div is definitely not. Instead this should be a button and it should have an aria-label, aria-expanded and aria-control.
    • This is not necessary, instead use JS to change the img of the button when the aria-expanded changes.
    <div class="header_menutoggle">
       <div ><img src="assets/icons/hamburger.svg" alt="" class="open"></div>
       <div ><img src="assets/icons/close.svg" alt="" class="close"></div>
    </div>
    
    • Lastly, the button should be inside the nav and it should be the first thing inside of it.
    • Whenever you remove the default styling for list elements, you are removing their semantic meaning. To correct this, you need to apply the role="list" to the ul/ol and the role="listitem" to the li.
    • For the logo, remove <div class="header_logo--wrapper">, it is unnecessary. Once that is fixed, the anchor element should have an aria-label stating only the sites name and and where it leads to; so in this case it would state "Scoot - Home".
    • All the background patterns, should be applied via CSS and not be present in the HTML. All you are doing it bloating your code.
    • The <section class="steps"> should have a visually-hidden heading and the <div class="steps_item"> should be built using the list element.
    • This <h2>Locate with app</h2>, <h2>Pick your scooter</h2> and <h2>Enjoy your ride</h2> should then be h3 headings.
    • The Apple and Google store should each be wrapped in an anchor element so users can then be directed to the appropriate store to download said app.
    • The footer logo should be wrapped inside and anchor element.
    • This <div class="footer_nav" role="navigation"> is unnecessary, especially when the nav element exist...
    • The social media icons aria-labels should only state the company names; "Facebook", Twitter" and "Instagram".
    • The <section class="values"> content should be built using the ordered list element.
    • For the "FAQs" section, personally, I would have used the details and summary element to make things easier, as they are fully functional and accessible. But if you really want to build it with JS, then it should look like this;
    <button
       class=""
       id=""
       aria-expanded=""
       aria-controls=""
       aria-label=""
    >Accordion One
    </button>
    
    <div class="">Content</div>
    

    You will then use JS to change the aria-expanded which will effect it styling.

    There is still a lot more that needs fixing (and I have not even look at you CSS/SCSS).

    If you have any questions or need further clarification, feel free to reach out to me.

    Good Luck and Happy Coding!

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