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

an animated react banking landing page

animation, react
Gift Richard•520
@fibonacci001
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


OMG you guys, I just finished another solo React project building this gorgeous Easybank landing page and can I get a high five?! 🖐️ Got those slick animations going, components breaking things into reusable bits - I'm basically a pro-React developer now! 😎

But let's get real - accessibility was kinda my weak point if I'm honest. 🤓 I was nerding out hard about toggle interactions and hover states when I should've been asking: but what about screen reader users?!

So I've gotta work on my inclusivity game for sho! Here's some ways I can have MORE fun (!) while making sites that work for errbody:

🔤 Semantic HTML is my BFF (but like cooler than my actual BFF maybe?)

🎨 Ooh baby those color contrasts are SPICY and accessible!!🌶️

📽 Alt text for images - now screen readers can enjoy my glorious creations too!

There's always more to learn when it comes to web access I know, but I'm so jazzed to keep improving. Because the web is for EVERYONE, am I right or am I right?? 🙌

My code organization is getting bonafide lit too - scoping CSS by component ftw! Less clashes than high school, woohoo! 💃 Sure I can tweak some things to share styles globally but I've come a long way from one messy CSS file, phew! 😅

So let me know if you've got tips for me my coding queens and kings! ✨ And high five to more inclusive and kick-butt websites for all users!! 🖐️🖐️ Raised hands AND hand clap emoji for the people in the back!! 🙌👏

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    enzmrg 💫•920
    @enzo-mir
    Posted over 1 year ago

    Awesome project the only things that i can say :

    • There is a lack of spacing between elements and line spacing
    • And careful to tabindex because the application is not really accessible be keyboard

    Well done this solution deserve compliments !

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