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

Minimal & Accessible Rating Component | Built with HTML, SCSS & JavaSc

accessibility, sass/scss, van-js
Abdulgafar-Riro•250
@Abdulgafar-Riro
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?

What I’m Most Proud Of: I’m proud of the clean structure, responsive layout, and smooth interaction using vanilla JavaScript. I also integrated SCSS for maintainable styling and ensured basic accessibility with ARIA roles.

What I’d Do Differently: Next time, I’d use native radio inputs for better accessibility, enhance keyboard navigation, and add subtle animations for smoother transitions.

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

Challenges & Solutions:

One challenge was managing the rating state across multiple buttons without a form. I resolved it using JavaScript to dynamically track and highlight the selected rating.

Another was ensuring accessibility with non-form elements. I used aria-pressed, role="radiogroup", and role="status" to improve screen reader support.

Styling with SCSS mixins also took some refining to keep the layout clean and responsive across devices.

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

None, But seeking someone who will help me with react.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    gkilasonia•380
    @gkilasonia
    Posted about 1 month ago

    Overall, good job. In your JS file, you assign a value to the selected rating paragraph when clicking on the rating buttons (better have them as radio buttons) before submitting. It means that value is changed every click before submitting, even though for that small portion of logic it is still better to assign value to the selected rating paragraph after clicking on the submit button

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