Results summary page

Hello there 👋. Congratulations on successfully completing the challenge! 🎉

• I have other recommendations regarding your code that I believe will be of great interest to you.

HTML 🏷️:

• This solution generates accessibility error reports, "All page content should be contained by landmarks" is due to non-semantic markup, which causes lacking of landmark for a webpage

• So fix it by replacing the <div id="main"> element with the semantic element <main> in your index.html file to improve accessibility and organization of your page.

• What is meant by landmark ?, They used to define major sections of your page instead of relying on generic elements like <div> or <span>

• They convey the structure of your page. For example, the <main> element should include all content directly related to the page's main idea, so there should only be one per page

HEADINGS ⚠️:

• This solution has generated accessibility error report due to skipping heading levels which warn us as "Heading levels should only increase by one"

• We want to avoid skipping heading levels, make sure to start with <h1> and working your way down the heading levels (<h2>, <h3>, etc.) helps ensure that our document has a clear and consistent hierarchy. Read more 📚

• Because skipping heading levels is a poor practice from the perspective of information design, whether we are talking about web pages, books, journal articles, or about anything else. You can not only confuse screen readers but all readers when you don't follow a consistent, logical pattern with your heading structure.

.

I hope you find this helpful 😄 Above all, the solution you submitted is great !

Happy coding!

hi Ohsand

this was great work from you. Now I want to work on the hover effect when i hover through the button referred here

<button id="continueButton">Continue</button>

We can reduce the opacity on hover to make the solution match the expectations of the design . Also I want to improve on mobile view to reduce the with of "main" class so that it does not take up the whole page

If you find my suggestions difficult to implement . You can join us for our weekly live streams where we assists other developers by providing helpful reviews and feedback with live Frontend mentor code edits and reviews on this link. Your solution will also be reviewed and edited by myself live link here >> https://youtube.com/live/L6WTd7HRTMM?feature=share

I don't think there's anything wrong with assigning each category an id and selecting them that way, but a way to do this without ids is via :nth-of-type pseudo-class. In your case, .summaryItem:nth-of-type(1) would select summary item for reaction, .summaryItem:nth-of-type(2) would select summary item for memory, etc.

Aside from that, I recommend looking into semantic HTML tags in order to fix warnings in accessibility report and make the website more accessible.