@FluffyKas
Posted
Hey,
Overall your solution looks really good! Responsiveness seems fine as well! I'm not quite sure about the animations you added to the navbar (for which you should perhaps use <nav> and not a div). They look a bit unnatural as they come down all the way from the top, crossing the cursor. Their origin should be the link you click on. And perhaps you could animate the opacity for them as well :) That's just probably personal taste though.
There are some issues here which are more important:
-
Why did you add aria-hidden to the nav links? You're hiding the whole navigation from screen readers which is probably not something you ever want to do...
-
For the arrow icons you could leave the alt text empty. Aria-hidden would be appropriate here.
-
The navbar links should not just look like links, you should use <a> for them (wrapped in those <li>s).
-
Your hamburger button should be a <button>. You can nest the image inside this (and leave the alt text empty).
-
Your page should have only one <h1> heading. For the rest you can go <h2>, <h3>... in a descending order. Heading levels play a major role in defining your page's outline.
-
Your footer links should also be <a> wrapped in those <li>s.
-
Everything that isn't inside your header or footer should be contained by a <main> landmark.
-
Not sure what a "down" attribute is but it's being picked up by the report as invalid.
-
Don't nest a <button> element inside an <a>. It's either a <button> OR an <a> element.
I hope this helped a bit with the accessibility issues. ^^
Marked as helpful
@abdraoufx
Posted
@FluffyKas Thanks For Your Awesome Feedback, And I Will Try To Fix These Small Problemes ^^ You Just Mention, And I Really Learn So Much From Your Feedback. Thanks.