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

Easybank landing page with Html, css and vanilla Javascript

Nguyen Duy•245
@koalalikecode
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello guys, This is a wonderful challenge for practicing layout skills. I have made adaptive mobile on my computer but I wonder why my phone's layout doesn't look like the PC's. I appreciate any advice and suggestions. Thank you!

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. Layout in desktop is good, and the mobile state seems fine. Though resizing, some elements are being too squished, especially the articles on the bottom part. You might want to adjust them, you could make a 2x2 layout for those in the responsive part before going in mobile layout, that would make the layout feel more great.

    Some suggestions would be:

    • The website logo in the header should have alt="easybank". The image itself already has the text, better using it. Also, avoid adding words that relates to "graphic" such as "logo, image, icon, picture".. as a alt value. Assistive tech will handle those for you.
    • The header links should be inside a nav and inside a ul element:
    <nav>
      <ul>
      { each link inside their own li element }   
      </ul>
    </nav>
    
    • request invite should be a link a tag and not button since it doesn't control anything in there. It would be button if it is modal, but it is more likely to be link.
    • The other request invite should be a tag as well.
    • On the articles section, it would be really great to make each article use an article tag and it should be inside a a tag:
    <a>
      <article>
       { element being wrapped by article }
      </article>
    </a>
    

    FOOTER

    • Website logo img tag should use alt="easybank".
    • The social media links should be wrapped inside their own a tag, because those are links. Each a tag should have aria-label pointing to what link it will go, like on the a that will wrap the facebook, it should have aria-label="facebook". They should be all inside a ul element as well, since they are list of social media links.
    • The other links should be inside a tag as well, but within the nav and ul like I mentioned above.

    MOBILE STATE

    • The hamburger menu should be using button element. Using img alone is not accessible.
    • The hamburger menu as well should have aria-label="hamburger dropdown toggler" like that, so that users will know what this button will do. It also should have aria-expanded attribute, changing the value of that in the javascript. That will inform the user that a dropdown has expanded.
    • The ordering of your hamburger dropdown toggler and the navbar links is wrong. The toggler should be before the navbar links in your html.

    Aside from those, great work.

    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

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