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

Animated & Semantic Interactive Rating Component Using Radio Buttons

accessibility, vite, animation
Gabriel Montplaisir•210
@GabrielMontplaisir
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first challenge I tackled w/ a form. I really wanted to make this semantically accurate, so opted to use the use the <input> element w/ radio buttons and took advantage of value, name, id. Unlike previous challenges where buttons were purely aesthetic, this button actually served a purpose.

Finally, I added my script at the end of my page before the </body> because this isn't the type of page which requires heavy JS.

Next, I took advantage of transition in my CSS to animate the buttons a little bit. I also used :checked to highlight the selection. Because of the Javascript, I had to use id, which isn´t something I often have to do when building static websites. It was a nice change of pace. I also decided to add an animation to move from one section to the next when the user selects a rating and gets the confirmation by creating some keyframes and sliding the page from right-to-left.

Having considerable experience w/ JS, it wasn't too difficult for me to figure out how to go about going from one section to the next. I opted for an Eventlistener to wait for the "click" and attributed the radio button's value to my selection. For a little extra, I decided to add a prompt if no selection is made to indicate to the user that they didn't select a rating. I simply hid the .hidden class where necessary. Because InnerHTML should be avoided where possible, I opted to use innerText instead.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Gabriel Montplaisir'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

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.