Latest comments
- @Kaviyaa88@Marcellino9
Nice work 👏
- @bobek1337What are you most proud of, and what would you do differently next time?
Im proud of responsiveness that I achieved, it was a hard task to make it work properly
What challenges did you encounter, and how did you overcome them?responsiveness was hard
What specific areas of your project would you like help with?Can I achieve same responsiveness with less code?
@Marcellino9nice work 👏👏
- P@Ira-Lis@Marcellino9
You can clearly see that it's a great job since the solution and the design are nearly identical down to the smallest detail. I have no words to say except, well done!
- @Hermodesign@Marcellino9
You can clearly see that it's well done since the solution and the design are almost identical down to a few centimeters. I have no words to say except, well played!
- @peterforster10@Marcellino9
1- Use a <section> with an aria-labelledby attribute to improve semantics and assist screen readers.
2- The image alt="Avatar of Jessica" is descriptive, but it repeats visible text (Jessica’s name in <h1>). 3- Use aria-label to provide more details about the links.
- @thomas-burnsideWhat are you most proud of, and what would you do differently next time?
This has given me confidence because I felt like I knew what I was doing and that it was relatively easy.
What challenges did you encounter, and how did you overcome them?I find navigating all the documents and readings and everything a bit hard to manage.
@Marcellino91- External Stylesheet – Move the inline should be inside a <header> section, and the <article> could use ARIA roles for better accessibility. 3- Invalid CSS Property – The height: default inside the media query is not valid; consider using auto or removing it.