Design comparison
Solution retrospective
I just learned about Tailwind CSS and decided to dip my toes into the workflow of doing Mobile-First Design.
Am I missing any best practices? I add the prescribed design system elements inside the tailwind.config.js and use the corresponding utility classes to use them.
Also, is my code semantically-ok? I made my title an <h2> because I'm assuming a <header> logo with an <h1> might be present in the website this component will be used.
Community feedback
- @0xabdulkhaliqPosted over 1 year ago
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.
HEADINGS ⚠️:
- This solution lacks usage of
<h1>so it can cause severe accessibility errors due to lack of level-one headings<h1>
- Every site must want only one
h1element identifying and describing the main content of the page.
- An
h1heading provides an important navigation point for users of assistive technologies, allowing them to easily find the main content of the page.
- So we want to add a level-one heading to improve accessibility by reading aloud the heading by screen readers, you can achieve this by adding a
sr-onlyclass to hide it from visual users (it will be useful for visually impaired users)
- Example:
<h1 class="sr-only">Order summary component</h1>
- If you have any questions or need further clarification, you can always check out
my submissionfor another challenge where i used this technique and feel free to reach out to me.
.
I hope you find this helpful 😄 Above all, the solution you submitted is great !
Happy coding!
0
Please log in to post a comment
Log in with GitHub
Join 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