Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Interactive Rating Card using Vanilla CSS and JS

Archi Halder•90
@archihalder
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was a very interesting project. I got to learn a lot. Here are few of the interactive things to notice -

  • If you submit without selecting any rating, the rating is 0
  • You can select only a one rating at a time
  • You can also deselect the rating by clicking it once again.

I know these are very basic logic, but it was fun to implement them in JS.

Now, here are some of the things I would love to get feedback on -

  1. I wanted to use a form and radio buttons for ratings, but was unable to style them, hence I used div.
  2. Some best practices for writing JS.
  3. Any other feedback about the project is also welcome !
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • IryDev•1,580
    @IryDev
    Posted almost 2 years ago

    Hey @archihalder, well done for completing this challenge 😄

    I will try to answer your questions :

    • Hiding Radio Buttons: Radio buttons can be visually hidden while maintaining their functionality using the layering and opacity technique. This would create a custom look while maintaining the radio button semantics.

    • Using Labels: Use <label> tags to enclose radio buttons and their text content. This will make it easier to select buttons even when clicking text.

    • Custom CSS Styles: Apply custom CSS styles for radio buttons, using properties like border, background, padding, margin, etc.

    Here's an example:

    HTML ;

    <div class="rating-container">
      <input type="radio" id="star5" name="rating" value="5">
      <label for="star5">5 Stars</label>
      
      <input type="radio" id="star4" name="rating" value="4">
      <label for="star4">4 Stars</label>
      
      <input type="radio" id="star3" name="rating" value="3">
      <label for="star3">3 Stars</label>
      
      <input type="radio" id="star2" name="rating" value="2">
      <label for="star2">2 Stars</label>
      
      <input type="radio" id="star1" name="rating" value="1">
      <label for="star1">1 Star</label>
    </div>
    

    CSS :

    .rating-container {
      display: flex;
      align-items: center;
    }
    
    .rating-container input[type="radio"] {
      display: none; /* Hide the default radio buttons */
    }
    
    .rating-container label {
      cursor: pointer;
      margin: 0 5px;
      font-size: 1.2rem;
      color: #999;
    }
    
    .rating-container input[type="radio"]:checked + label {
      color: #ff9800; /* Change color when radio button is checked */
    }
    
    

    I hope you'll find this helpful😄

    Marked as helpful

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
Frontend Mentor logo

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