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

Easybank landing page

sass/scss, accessibility
Mr Rabbit•1,020
@rabbitmaid
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I learned a lot from this exercise. I had difficulties positioning the hero image and also how to make sure all my article boxes have the same height regardless of the description length

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Kamel•1,190
    @hmadamk
    Posted almost 3 years ago

    to solve your accissibility issues and Html issues you need to do the following

    1. Header does not need a role it's a header so that's already define it
    2. your section shouldn't have a role, role is specified for certain things to learn more about roles check mdn it should have aria-role for screen readers
    3. your page must have one section to be instead of a section to the main-element this should be the most important section like the hero one
    4. don't leave the srcset empty
    5. if the img is not for decorating the page you should but a description for it in the alt attribute
    6. your page must have one h1 element holding the main idea of your site you could wrap the img at the .header__logo with an h1 and then remove the margin from it what this does is that it assign the value of the alt to the h1 which mean your page is more search engine friendly
    7. you should use h2-h6 at least one into all of your sections happy coding hope this helped if it did help you consider marking this comment as helpful
    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
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