Design comparison
SolutionDesign
Solution retrospective
I had some issues getting the color for the active states, I had to use a color picker to get the color from the design files. Did anyone else face the same problem?
Community feedback
- @pikapikamartPosted about 3 years ago
Hey, great work on this one. Layout in general looks great and adaptive for mobile.
I haven't tackled this challenge yet so don't really know about the issue that you said.
For suggestions, here are some:
- Avoid using
height: 100vh
on a large container like the.container
as this makes the element's height capped based on the viewport/screen's height. Instead usemin-height: 100vh
so that the element will expand if it needs to. - Always have a
main
element to wrap the main content of the site. For this usemain
tag on the.container
selector. - The illustration in here is only decoration. Decorative images should be hidden for screen-reader at all times by using
alt=""
andaria-hidden="true"
to theimg
tag or onlyaria-hidden="true"
if the image is usingsvg
. - Only use descriptive
alt
on images that are meaningful and adds content to the site otherwise hide the image for screen-reader users. - When using
img
tag, you don't need to add words that relates to "graphic" such as "illustration" and others, sinceimg
is already an image so no need to describe it as one. - Always have an
h1
on a page. For this one, temporarily you could useh1
on theorder summary
instead ofh2
. But for a better usage ofh1
,have a look at Vanza's solution on this one. On this solution, you will see a screen-reader onlyh1
usage. See how it is used and the stylings applied to it. - The music-icon should be hidden as well so use the method I mentioned above.
- The
annual-plan
and the pricing below it are 2 separate text. Theannual-plan
should/could useh2
since it gives information on what the section contains and usep
tag on the pricing.
Aside from those, great job again on this one.
Marked as helpful0@AchigyusPosted about 3 years ago@pikamart Thank you for your kind words, I've updated my solution with the your suggestions
1 - Avoid using
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