Design comparison
Solution retrospective
Hi everyone,
This is my solution for 3-column-preview-card challenge.
All suggestions and advice are welcome.
Thanks in advance.
Community feedback
- @pikapikamartPosted about 3 years ago
Hey awesome work on this one. Desktop layout looks really great, it is responsive but at point before the mobile breakpoint, the layout is squished like on size 690px. Mobile state look great but the layout could use bit more width:>
Some other suggestions would be:
- Always have a
main
element to wrap the main content of your page. On this one, the.wrapper
should be using themain
instead ofdiv
. - Also on the
.wrapper
I would usemax-width
instead ofwidth
likemax-width: 900px
andwidth: 100%
so that it will adapt more to narrow-screen-size and having somepadding
on the left and right side of thebody
. - Those car icons could use an extra
aria-hidden="true"
attribute on it so that it will be totally hidden for screen-reader users. - Avoid using multiple
h1
on a page, use only at least 1 per page so change those into other heading tags. - A page must have a single
h1
on a page. Since there are no text-content that are visible that could beh1
, you will make theh1
screen-reader only text. Meaning this will be hidden for sighted users and only be visible for screen-reader users, search aboutsr-only
stylings and see how it is used. Theh1
text should describe what is the main content is all about, thish1
would be placed as the first text-content inside themain
element. Have a look at Grace's solution on this one. Inspect the layout and see the usage of theh1
as well the stylings applied to it. - When using
a
tags, remember to add thehref
attribute in order for thea
tag to work properly.
Aside from those, great job again on this one.
Marked as helpful0@MirosBL45Posted about 3 years ago@pikamart Hi, it really means a to me you feedback. I saw Grace's solution, it is very good job. I did not know for h1, but it have sense, I will do like that in future.
Also, I have to work on screen-reader users and mobile breakpoint.
Thanks a lot on your advice. I am new, and this is helpful for me.
1 - Always have a
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