Submitted 4 months agoA solution to the Results summary component challenge
Mobile-first responsive, accessible summary stats
accessibility, bem, pure-css
@haquanq

Solution retrospective
What are you most proud of, and what would you do differently next time?
I decided to refactor old solution, improved CSS by using reusable variables, better class naming (BEM). Most important, i have improved accessibility of the component, for example 50 / 100
will be read by screen readers as score: 50 out of 100
by using hidden text while visually 50 / 100
will be hidden from screen readers.
is my HTML structure ok? what about its accessibility?
Code
Loading...
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Ha Quang's solution.
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