Design comparison
Solution retrospective
Another special attention given to this project, with few additional features/animations. Just to make it a bit more attractive and appealing whilst reinforcing what I learned so far. As always, every additional task/feature suggestion would be taken into account. Thanks again in advance for all the feedback.
Community feedback
- @ApplePieGiraffePosted about 2 years ago
Hello, Zdravko! 👋
Good job on this challenge! 👏
A couple of things I suggest are,
- Setting the
alt
text for the star icons to be an empty string so that they will be ignored by screen readers. That’s because those elements aren't so necessary or important to the content of the page and as a result doesn’t need to be read by screen readers (which can be annoying for users if screen readers are reading out thealt
text for every single star). 😅 - Adding
overflow-x: hidden
to thebody
to prevent any unwanted horizontal scrolling on the page. - I think adding the decorative background images with CSS background images to the
body
of the page will do (there's no need to add extradiv
s for those images). You can simply add both of them to thebody
of the page. See this helpful article for how to use multiple CSS background images:
Hope you find these suggestions helpful. 😊
Keep coding (and happy coding, too)! 😁
Marked as helpful3@Zdravko93Posted about 2 years agoHello @ApplePieGiraffe, and thank you for your helpful suggestions. I will edit my code according to them, and have those tips in mind while building my next project. Thanks again :)
1 - Setting the
- @vanzasetiaPosted about 2 years ago
Hello, Zdravko! 👋
Congratulations on completing this challenge! 🎉
Here are some suggestions for improvements.
- For the background patterns, I recommend making them as background images of the
body
element. This way, you can remove thosediv
elements from the HTML. - Avoid using
br
elements for presentational purposes. Read the "Accessibility concerns" part of the MDN documentation forbr
. - Make the
span
block element instead usingdisplay: block
. - There's no need to wrap each
img
withfigure
element. The only reason to usefigure
is if you need to include afigcaption
. Otherwiseimg
tag is fine. - If the
figcaption
is empty then, I would not wrap theimg
withfigure
element. - All the star icons are decorative images. So, leave the alternative text empty (
alt=""
). - I recommend taking a look at "Quick tip: Using alt text properly - The A11Y Project".
- Don't use
aria-hidden="true"
onsection
! The screen reader users will not know that there's a testimonial from Colton Smith. Also, it's best to not use ARIA attributes. Remember that, No ARIA is better than Bad ARIA. - Headings must be in a logical order. I recommend reading the "How-to: Accessible heading structure - The A11Y Project" article to learn how to use headings correctly.
I have two recommended videos. The first one is telling how hard HTML is (HTML is not easy). The second one is talking about HTML and modern CSS.
- Manuel Matuzović - Lost in Translation - YouTube
- Andy Bell – Be the browser’s mentor, not its micromanager - YouTube
I suggest visiting Solid Start. It gives you an overview of web accessibility.
I hope this helps! Happy coding!
Marked as helpful2@Zdravko93Posted about 2 years ago@vanzasetia Hello! First of all - thanks for taking time to review my code. I will do as you suggested and improve it accordingly. Thanks again!
0 - For the background patterns, I recommend making them as background images of 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