Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
20
Comments
289

Finney

@Finney06NIGERIA3,010 points

A Gen-Z trying to find his way around tech.

I’m currently learning...

Everything😏

Latest solutions

  • Article preview component

    #accessibility

    Finney•3,010
    Submitted over 1 year ago

    0 comments
  • Rate-It: Simple and Engaging Rating Interactive.

    #accessibility#animation

    Finney•3,010
    Submitted over 1 year ago

    0 comments
  • Interactive FAQ Accordion with Smooth Animation using HTML, CSS, & JS.

    #accessibility#animation

    Finney•3,010
    Submitted over 1 year ago

    0 comments
  • Desktop Design news homepage (yet to be responsive).


    Finney•3,010
    Submitted about 2 years ago

    1 comment
  • Responsive Clipboard landing page using CSS grid (Mobile first)

    #accessibility

    Finney•3,010
    Submitted about 2 years ago

    0 comments
  • Mobile first Responsive Result Summary Component

    #accessibility

    Finney•3,010
    Submitted over 2 years ago

    2 comments
View more solutions

Latest comments

  • Yonten•340
    @yozidst
    Submitted over 1 year ago

    Interactive - Rating Component

    #animation
    1
    Finney•3,010
    @Finney06
    Posted over 1 year ago

    Love the animations, just learnt something new.

  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Submitted over 1 year ago

    FAQ accordion (Tailwind CSS)

    #accessibility#animation#pwa#tailwind-css#lighthouse
    7
    Finney•3,010
    @Finney06
    Posted over 1 year ago

    Isn't the button meant to close when another button is been click...?

  • Musa•260
    @musanurbadr
    Submitted about 2 years ago

    social-proof

    2
    Finney•3,010
    @Finney06
    Posted about 2 years ago

    Hello Musa 👋. Good job on completing the challenge !

    Here are some suggestions regarding your code that may be of interest to you.

    HTML 🏷️:

    To clear the Accessibility report:

    The error message "ul and ol must only directly contain li, script, or template elements" typically appears when there is invalid HTML markup in the code. This error indicates that either an <ul> or <ol> element contains an element other than <li>, , or <template> elements as direct children.

    • If you need to include other types of elements within a list, you can nest them within an <li> element.

    • Use a validator tool to check your HTML code for other possible errors.

    Here's an example of valid HTML markup for an ordered list:

    <ol>
      <li>Item 1</li>
      <li>Item 2</li>
      <li>Item 3</li>
    </ol>
    

    And here's an example of valid HTML markup for an unordered list:

    <ul>
      <li>Item 1</li>
      <li>Item 2</li>
      <li>Item 3</li>
    </ul>
    

    By ensuring that your HTML markup follows the specifications, you can avoid errors and ensure that your web page is accessible to all users.

    • The error message "All page content should be contained by landmarks" typically appears when the HTML code does not contain the necessary accessibility landmarks to help users navigate the content of the page. In this case, the <div> element with class "attribution" is not a landmark or a footer element, and therefore it does not provide any navigation aid for users.

    To fix this error, you can do the following:

    • Use HTML5 landmarks: HTML5 introduced several new elements that can be used to define the different sections of a web page, such as <header>, <nav>, <main>, <aside>, and <footer>. By using these elements, you can create a clear hierarchy of content that is easy to navigate for users.

    • Include a footer element: A footer element should be included at the end of the document and contain information about the website or document, such as copyright information or contact details.

    Here is a [**web accessibility evaluation tool**](https://wave.webaim.org/)📕 to check your webpage for any remaining errors or warnings related to landmarks.
    
    I hope you find it helpful!😏 Above all, the solution you submitted is 👌.
    🎉Happy coding!
    
    Marked as helpful
  • Aymeric Ratinaud•80
    @aratinau
    Submitted about 2 years ago

    Fylo data storage component

    1
    Finney•3,010
    @Finney06
    Posted about 2 years ago

    Hello Aymeric 👋. Good job on completing the challenge !

    Here are some suggestions regarding your code that may be of interest to you.

    HTML 🏷️:

    To clear the Accessibility report:

    • Images should have alternate text. <img class="img-bubble" src="images/icon-upload.svg" alt="upload icon"> this provides alternative text descriptions of images for people who are visually impaired and rely on screen readers to navigate the web. Screen readers can read the alt text aloud, enabling these users to understand what the image represents and how it relates to the content on the page. Overall, including alt text in HTML is an important best practice for creating accessible and user-friendly web content.

    • Wrap the page's whole main content in the <main> tag.

    • Always avoid skipping heading levels; Starting with <h1> and working your way down the heading levels (<h2>, <h3>, etc.) helps ensure that your document has a clear and consistent hierarchy.

    • Use HTML5 semantic elements such as <header>, <nav>, <main>, <aside>, and <footer> to define these sections.

    I hope you find it helpful!😏 Above all, the solution you submitted is 👌. 🎉Happy coding!

    Marked as helpful
  • Melvin Nacfil•180
    @mnacfil
    Submitted about 2 years ago

    Multi Step form build with React, Styled-components, Context API

    #styled-components#react
    2
    Finney•3,010
    @Finney06
    Posted about 2 years ago

    Hello Melvin👋. Good job on completing the challenge !

    Here is a suggestion regarding your code that may be of interest to you.

    HTML 🏷️:

    To clear the Accessibility report:

    • Always avoid skipping heading levels; Starting with <h1> and working your way down the heading levels (<h2>, <h3>, etc.) helps ensure that your document has a clear and consistent hierarchy.

    I hope you find it helpful!😏 Above all, the solution you submitted is 👌. 🎉Happy coding!

  • Jalal-Aljhny•340
    @Jalal-Aljhny
    Submitted about 2 years ago

    Responsive simple dashboard with theme switcher using Grid

    2
    Finney•3,010
    @Finney06
    Posted about 2 years ago

    Hello Jalal-Aljhny 👋. Good job on completing the challenge !

    Here is a suggestion regarding your code that may be of interest to you.

    HTML 🏷️:

    To clear the Accessibility report:

    • Always avoid skipping heading levels; Starting with <h1> and working your way down the heading levels (<h2>, <h3>, etc.) helps ensure that your document has a clear and consistent hierarchy.

    I hope you find it helpful!😏 Above all, the solution you submitted is 👌. 🎉Happy coding!

    Marked as helpful
View more comments
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

Mentor of the Week - 3rd Place

This badge is awarded to the 3rd placed community member on the weekly Wall of Fame.

Fun fact

The Hansen Writing Ball shown in the badge was the first commercially produced typewriter. It was put into production in 1870 with its unique ergonomic design. It was overtaken in the market in 1873 by the Sholes and Glidden typewriter which was the first keyboard to utilise the QWERTY layout we now use today.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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