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

Responsive Landing page using Flex and Sass, and interactions using JS

Francel•370
@Haemoffy
A solution to the Bookmark landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedbacks will be acknowledge, especially any feedbacks about my usage of ARIA attributes

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    And about aria...

    You have used aria-describedby quite often but you may have got confused and did everything opposite of how it was suppose to be...

    Lemmi explain...

    Describedby simply mean something is described by something else

    When you put that aria on an element, then it will take the id of another element that is describing that element and you have been doing the opposite...

    A paragraph will describe a heading and not the opposite...So

    You should put aria-describedby="id of paragraph" on heading...

    Good luck

    You can visit MDN for more info

  • Roc Tanweer•2,500
    @RocTanweer
    Posted about 4 years ago

    Hello 👋

    Great work 👌 and quite extensive use of arias...

    I just reviewed you index.html file and it was really impressive..! I also made the same project but your work is too good...

    But I wish to point out some things...

    • In feature tab section, the tab changers are suppose to be buttons and not h tags... Because users are clicking on them and something is happening

    • When you put an icon in a link, you should put a span in the link with text describing the icon and adding sr-only class to that span. All these for accessibility purpose.

    <a><span class="sr-only">Facebook icon</span>icon here...</a>
    

    You can download sr-only class from Google...

    Hope it helps 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