Design comparison
Solution retrospective
This challenge is really made me crazy. I realised how little I know about responsive images.
Please leave a feedback to improve my frontend skills.
Community feedback
- @pikapikamartPosted about 3 years ago
Hey, great work on this one. Layout in desktop seem fine, for the mobile layout, the sections that includes the fruit images is too large, occupying all the screen's height, toning it down would be really great.
Some suggestions would be: DESKTOP
- On the
header
lose the word "link" on thearia-label
, since it is already a link, screen reader will announce it for you,aria-label="homepage"
will work just fine. - The navbar could have used
ul
element, so that screen reader users will know how many links there are in the navbar, since screen readers announces how many items there are inside the list. - The
alt
text for thearrow-down
could have been left emptyalt=""
since it is just a decorative image. - On the
learn more
links, you will notice that it takes the whole width of the its parent, try tabbing on it, you will see that theoutline
is at full width. Instead to prevent this, usewidth: max-content
on thea
tag. This will limit itswidth
based on the content inside it, like it's supposed to do. - On the testimonial section, the name of the person could have been wrapped inside a heading tag. Why, because if I navigated through the testimonial section and I encounter the heading tag of the person, I would know that there a testimonial content is being binded to that heading, binding to that person.
footer
sunnyside link as well could usearia-label="homepage"
.- The sunnyside logo in the
footer
should havesr-only
text inside it so that it would have a text that will be read if screen reader navigate to it, if you want thesvg
to be hidden, usearia-hidden="true"
attribute on thesvg
. - The 3 links in the
footer
could have been insideul
as well. - The social media links as well could have been inside
ul
element. Thearia-label
should only contain the name of the social media, likearia-label="facebook"
.aria-hidden
on the social media linkssvg
could be great as well.
MOBILE
- The hamburger menu should use a
button
element instead ofa
tag, because that hamburger menu is just a control element and not a link element right. - Hamburger menu as well should have been using
aria-expanded
attribute so that users will know if the dropdown has shown or not. - The
img
inside the hamburger menu should usealt=""
because you don't want the user to navigate in thatimg
. Thebutton
will create the sense. - Navbar on the dropdown as well should have been inside
ul
element.
Aside from those, you did really great in here.
Marked as helpful1@logistusPosted about 3 years ago@pikamart I did all the suggestions except fruit image sections.
In order to show the text below the fruit images, I needed to add 150% padding-bottom. If there is another way to succeed, please tell me.
Also, in the mobile design image, those sections have a 600px height. In my design at 375px width resolution, those sections have a 562.5px height.
I'm not saying it looks good, it looks weird and way too long as you mentioned, but it is what I saw in the design image file.
Thanks a lot for the suggestions.
0@pikapikamartPosted about 3 years ago@logistus Hey, for that part, on the
fruit-image-text
, you are referring for mobile state right.Since you are using grid, you could have just set the height of those grid-items right. Making the custom size in the
grid-template-rows
property. I rarely usegrid-template-areas
too hard to handle I think.Using the
grid-template-rows
give the explicit height of the 2 fruit container at the bottom. That way, you won't need to addpadding-bottom
on it, because the grid parent will give it the proper height it need.0 - On the
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