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

Interactive Rating Component with vanilla JS

P
turtlewords•470
@Turtlewords
A solution to the Interactive rating 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?

I made sure to use semantic elements where possible and assign aria roles to certain interactive elements.

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

Styling the radios as buttons was a bit of a challenge. Hiding the input and styling the radio allowed me to achieve the desired effect.

What specific areas of your project would you like help with?

Responsiveness, design accuracy, and functionality. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • denise•530
    @moncadad
    Posted about 1 month ago

    If it wasn't for the side by side I'd assume it was perfect. Responds well, the code is well structured as well as it's functionality. You did a great job!

  • Harsh Kumar•3,490
    @thisisharsh7
    Posted about 1 month ago

    Great job! You've implemented a clean, interactive, and accessible rating component using semantic HTML, ARIA roles, and modern CSS techniques. Here's detailed feedback:

    ✅ What You Did Well:

    • Excellent use of semantic elements like <main>, <section>, and <fieldset>.
    • Proper keyboard accessibility with tabindex and keypress events.
    • Custom-styled radio buttons are intuitive and visually appealing.
    • Gradient background and button styling are consistent with the design challenge.
    • Clear separation of layout (CSS) and behavior (JavaScript).

    🛠 Suggestions:

    1. Move <input> before <label> and use for and id to associate correctly — improves screen reader support.

    2. Use a submit event listener on the <form> itself instead of just the button to enhance accessibility.

    3. Match spacing more precisely with the original design spec (Frontend Mentor often gives Figma files).

    Fantastic work overall — you're building strong front-end fundamentals. Keep going! 🚀

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

Oops! 😬

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

Log in with GitHub