![](https://res.cloudinary.com/dz209s6jk/image/upload/f_auto,q_auto,w_900/Screenshots/jw8werivycy4bnbmof1t.jpg)
Design comparison
Solution retrospective
I am proud of maintaining a solid understanding of HTML and CSS basics. It’s rewarding to see that my foundational knowledge remains strong. Next time, I would like to focus on adding more accessibility features, such as ARIA roles, to ensure my projects are more inclusive and user-friendly.
What challenges did you encounter, and how did you overcome them?I encountered two minor challenges, which are documented in the README file of this project. The first challenge was figuring out how to add borders to our table rows. After some research, I found a Stack Overflow thread that explained the necessity of using the border-collapse: collapse; property in the table styling to effectively apply borders to table elements. The second challenge wasn't really a hurdle but rather a noteworthy discovery: the usefulness of the "contains" attribute selector in CSS. This selector has proven to be very handy in targeting elements that contain specific text.
What specific areas of your project would you like help with?I want help with expanding the accessibility features of my project. While I have a basic understanding of HTML and CSS, I want to ensure that my project is as inclusive and user-friendly as possible. Specifically, I seek guidance on implementing ARIA roles, enhancing keyboard navigation, improving screen reader compatibility, and ensuring color contrast meets accessibility standards. Any advice or resources on best practices for accessibility would be greatly appreciated.
Community feedback
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