Design comparison
Solution retrospective
I would like some reviews,advices about my design and code, thank you guys so much :3
Community feedback
- @pikapikamartPosted about 3 years ago
Hey, great work on this one. The desktop layout looks great and that animation was really really good. The responsive state could be better because there are section where the text are hard to read because the color are the same with the background-image's color. The mobile state don't have the hero-section, but looks fine in layout, but missing on that.
Some other suggestions would be:
- On the
header
, the links should be inside thenav
element, since those are your website's navigational links. - Each navlinks should be inside their own
a
tag, because those are supposed links, always use interactive elements for interactive components like the links. - The
alt
for the arrow-icon image should be left empty likealt=""
since it is only decorative. Decorative images should be usingalt=""
attribute as well as addingaria-hidden="true"
on the element, meaningful element on the other hand needs meaningfulalt
. - On the
main
section, you are using too muchsection
element, for example, the first content, the egg image and the text on it's left side, you could have only used 1section
justdiv
on it. For this one, I would just use 1section
element to wrap all the contents but not including the testimonial, that will be anothersection
. learn more
should be usinga
tag since it is supposed to be a link.- The
alt
for each person's image should be using their name as the value likealt="Emily R"
. When usingalt
attribute, avoid using words that relates to "graphic" such as "avatar, icon, image.." no need to describe it as an image, it is already one. - Name of the person per testimonial could have used a heading tag.
- The
decorate
selector should be include inside themain
element.
FOOTER
- Avoid using multiple
h1
on a single page, only use at least 1 per page. The sunnyside could have use another heading tag. - The links below the sunnyside could have been wrapped inside a
nav
element, since those are still your navigational links. - Again, use
a
tag for the links. - On the social media links, those shouldn't be wrapped by
nav
element, since those are not your website's navlinks. - The social media could have used
ul
element, since those are "list" of links. Eacha
tag must havehref
attribute on it, so that it will function properly. - Each
a
tag for the social media should have eitheraria-label
attribute or ansr-only
text inside thea
tag, describing where the link would take them. For example, on the facebook link, you should use "facebook" as the value for whatever technique I mentioned that you want to use. - Each
img
for social media should havealt=""
andaria-hidden="true"
since those are only decorative images.
MOBILE
- Lacks the hero-section, you might want to check that one out.
- The hamburger menu should have use
button
element, again, interactive component.
SUPPOSING BUTTON IS USED
- The
button
should have eitheraria-label
attribute orsr-only
text inside it, like on the footer, describing what thebutton
does, an example text could be "navigation menu dropdown". - The
button
should also be usingaria-expanded
attribute on it. Usingfalse
as default value then changing totrue
if thebutton
is toggled then vice-versa.
Aside from those, great work on this one.
Marked as helpful1@docuong0912Posted about 3 years ago@pikamart really detail explaination, i am looking for this comment :D , thank you so much, i was wondering about the section part,it's clear now thanks to you, most of your suggestions are helpful to me
0 - On the
- @GerriEzeochaPosted about 3 years ago
Looks like you're missing your main hero section! I was looking through your src and public files and cant seem to identify the issue.
1@docuong0912Posted about 3 years ago@GerriEzeocha oh no, i totally forgot about it, thank you for reminding me
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