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

Easybank landing page with vanilla stuff

accessibility
Fluffy Kas•7,675
@FluffyKas
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys,

This challenge turned out to be a lot harder than it seemed at first glance! Lots of layout and accessibility problems I had to solve but I learned heaps and really had fun completing this project.

Inspired by Kevin Powell's recent video, I added a Skip navigation button as well.

I'd be very happy to hear some feedbacks (especially regarding accessibility and HTML)! Was also wondering, if I should add animations to the page but then decided against it as I kinda like the clean looks of the design (also unsure how much animation a banking app should have^^). What do you think?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kazuya•30
    @zenStroke
    Posted over 3 years ago

    Hi FluffyKas,

    Great job on completing the challenge!

    I had a look at the live version of your site and overall, I think you did great. There were a few minor issues.

    I assume it looks fine on your monitor, but on my 13 inch macbook it seems like there are some scaling/responsiveness issues. The request invite button under 'Next Generation Digital Banking' actually goes below the grey part and enters the next section. Sadly, I am not well-versed in responsive design yet and cannot give you tips on how to improve this.

    Similarly, the mockup image overflows to the right. I think this can be fixed if you add overflow: hidden; to the parent element of the image.

    Other than that, you managed well! I did the same challenge, and it took around 4 days to complete. If you don't mind, I would appreciate it if you could have a look at my site from your perspective and provide me with some feedback. (note: I haven't optimized for mobile yet)

    Also, if you would like, I can send you a screenshot of what I see in my screen of your site in the slack channel if you are in there.

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