Design comparison
Solution retrospective
š Features: āŖļø Responsive (mobile-first) āŖļø Resemblance with the original design āŖļø Organized folder structure and code base well maintained with prettier
āļø Build with: āŖļø React JS āŖļø Sass āŖļø Vite
Any feedback is appreciated šš¾
Community feedback
- @0xabdulkhaliqPosted 11 months 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.
HTML š·ļø:
- The <main> element behaves like a main landmark role. Landmarks can be used by assistive technology to quickly identify and navigate to large sections of the document.
- Here you just declared role="main" for main element which is already a semantic element by default. Adding explicit role on a semantic element is just like a bloatware for no reason, We can follow up the efficient way which is simply the
main
element.
- So you can refactor the
<main role="main">
to<main>
.
I hope you find this helpful š Above all, the solution you submitted is great !
Happy coding!
Marked as helpful0@DagimTizazuPosted 11 months agoThanks @0xAbdulKhalid , I just fixed it by adding the role attribute to the hero area container div. I think it makes more sense in this case I guess
0
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