Design comparison
Solution retrospective
Hey everyone I'm very new to these challenges, so open to any kind of suggestions to make my HTML & CSS skills more polished.
Community feedback
- @Bayoumi-devPosted over 2 years ago
Hey Surajit, Congratulations on completing this challenge... It looks good!
My suggestions:
Document should have one main landmark
, Contain the component with<main>
.
<main> <div class="card"> //... </div > </main>
-
Page should contain a level-one heading
, Changeh3
toh1
, You should always have oneh1
per page of the document... in this challenge, you will useh1
just to avoid theaccessibility issue
that appears in the challenge report... but don't useh1
on small components<h1>
should represent the main heading for the whole page, and for the best practice use only one<h1>
per page. -
Use
Font-Family: Outfit
as recommended in this challenge to get it looking as close to the design as possible.
Hope this is useful to you... Keep codingπ
Marked as helpful1@SURAJITSHAWPosted over 2 years ago@Bayoumi-dev Thanks for the suggestions man. You guys are so supportive. I'm about to implement your suggestions to fix the accessibility issues. Thanks again for your time to look at this and give genuine suggestions βοΈβοΈ
0 - @SamadeenPosted over 2 years ago
Hey!! Cheers π₯ on completing this challenge.. .
Lets firstly work on your accessibility issues.
Document should have on main landmark
basically means your html should be structured more semantically and the correct format should be your<header>......</header>
followed by your<main>......</main>
and lastly your<footer>....</footer>
hence you should use<main class="card">
instead of<div class="card">
.Page should contain a level-one heading
basically means yourhtml
should have ah1
it aid navigation hence<h3>Improve your front-end skills by building projects</h3>
should be<h1>Improve your front-end skills by building projects</h1>
and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.
This should fix most of your accessibility issues.
. Regardless you did amazing... hope you find this helpful... Happy coding!!!
Marked as helpful1@SURAJITSHAWPosted over 2 years ago@Samadeen thanks man, I couldn't figure out what to do to fix the accessibility issues. You're the savior ππ
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