Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive solution using Tailwind CSS

tailwind-css
shitij_kpn•80
@shitij-kpn
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Restarting my webdev journey this really helped me get my confidence back and I am happy that I was able to complete this challenge.

What challenges did you encounter, and how did you overcome them?

Trying to form the mental model to complete this challenge was the hard part.Figuring out what structure of HTML should I go with and how to place the items in a particular way was also hard.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rupali•890
    @rupali317
    Posted about 1 year ago

    Hello @shitij-kpn. Great work on your first challenge.

    I have the following suggestions for your code where you can improve the accessibility of your project

    • There are keyboard users who will use "Tab" or "Shift+Tab" to navigate across the page. When I use the tab key, the button in your page gets highlighted but the highlight color can be changed to make it more visible to the eye. :focus-visible will get the job done
    button:focus-visible {
      outline:none;
      box-shadow: 0rem 0rem 0rem 0rem 0.25rem hsl(39, 64%, 57%)
    }
    
    • I used the screen reader to read the entire content of your page. I noticed that for the part where there are 4 items the screen reader reads the icons as image. When users who rely on screen readers encounter "image" word, it might cause confusion. If these icons are just for decoration, you can have the role="presentation" attribute for the SVG tag. In that way assistive technology will ignore reading the SVG.

    Hope that helps!

    Marked as helpful
  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 1 year ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have a suggestion regarding your code that I believe will be of great interest to you.

    GRADIENT BACKGROUND DURING HOVER :

    • Looks like the component button hover state background got a solid color instead of gradient colors. We need to fix this!

    • Just add the following tailwind utility classes
    hover:bg-gradient-to-r from-purple-600 to-indigo-600
    

    • Now your component's button background for hover state has been set properly

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub