Design comparison
SolutionDesign
Solution retrospective
Great project, super fun! :)
Community feedback
- @PhoenixDev22Posted about 2 years ago
Hello KULEK,
Your solution looks great. I have some suggestions regarding your solution, if you don't mind:
- It's recommended to avoid creating duplicate content (eg: duplicate navigation). You can style the same navigation in mobile and desktop differently using media queries. Practice like this can result in a poor user experience, when a visitor finds substantially the same content repeated within a set of search results.
- I suggest to put the nav links within an unordered list structure so that a screen reader will read out how many things are in the list to give visually impaired users the most information possible about the contents of the navigation.
- To ensure that the landmarks are unique, you should add
aria-label=”secondary “
oraria-label=”footer”
to<nav>
in the<footer>
. A brief description of the purpose of the navigation, omitting the term "navigation", as the screen reader will read both the role and the contents of the label.
The
nav
element in the header could use anaria-label="primary"
oraria-label=”main”
attribute on it. The reason for this is that, you should add thearia-label
for a nav element if you are using the nav more than once on the page.you can read more in MDNAside these, excellent work! Hopefully this feedback helps.
Marked as helpful0
Please log in to post a comment
Log in with GitHubJoin 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