Finney

Latest comments

• 

  Yonten•340

  @yozidstSubmitted over 1 year ago

  

  Interactive - Rating Component

  #animation

  1

  110
  

  Finney•3,010

  @Finney06Posted over 1 year ago

  Love the animations, just learnt something new.

  1
• 

  Melvin Aguilar 🧑🏻‍💻•61,060

  @MelvinAguilarSubmitted over 1 year ago

  

  FAQ accordion (Tailwind CSS)

  #accessibility#animation#pwa#tailwind-css#lighthouse

  7

  1599
  

  Finney•3,010

  @Finney06Posted over 1 year ago

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

  1
• 

  Musa•260

  @musanurbadrSubmitted about 2 years ago

  

  social-proof

  2

  50
  

  Finney•3,010

  @Finney06Posted 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

  0
• 

  Aymeric Ratinaud•80

  @aratinauSubmitted about 2 years ago

  

  Fylo data storage component

  1

  51
  

  Finney•3,010

  @Finney06Posted 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

  0
• 

  Melvin Nacfil•180

  @mnacfilSubmitted about 2 years ago

  

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

  #styled-components#react

  2

  60
  

  Finney•3,010

  @Finney06Posted 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!

  0
• 

  Jalal-Aljhny•340

  @Jalal-AljhnySubmitted about 2 years ago

  

  Responsive simple dashboard with theme switcher using Grid

  2

  30
  

  Finney•3,010

  @Finney06Posted 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

  0