Design comparison
SolutionDesign
Solution retrospective
What are you most proud of, and what would you do differently next time?
I am proud of the way I used Grid to order the testimonials.
What challenges did you encounter, and how did you overcome them?I didn't find any challenge very hard to overcome.
What specific areas of your project would you like help with?In the responsive part.
Community feedback
- @Mateogr03Posted 3 months ago
-
Does the solution include semantic HTML?
- Yes, the solution includes semantic HTML. It uses tags like
<header>,<main>, and<footer>to structure the content meaningfully.
- Yes, the solution includes semantic HTML. It uses tags like
-
Is it accessible, and what improvements could be made?
- The solution is fairly accessible, with appropriate use of alt text for images and semantic HTML. Improvements could include ensuring that interactive elements are keyboard accessible and adding ARIA roles for enhanced accessibility.
-
Does the layout look good on a range of screen sizes?
- Yes, the layout is responsive and adapts well to different screen sizes, ensuring a good user experience on mobile, tablet, and desktop devices.
-
Is the code well-structured, readable, and reusable?
- The code is well-structured and follows good practices in terms of class naming and CSS organization. It is readable and modular, making it reusable for similar projects.
-
Does the solution differ considerably from the design?
- The solution closely follows the provided design, with only minor differences in styling that do not significantly affect the overall look and feel.
0 -
Please log in to post a comment
Log in with GitHub
Join 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