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

Interactive Rating Component with basic js

Biruk Moges•280
@lost50U1
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


any suggestions and comments appreciated i used basic javascript to make it work but i want to learn the right way of using to make it work so any suggestions are useful resource to the javascript part will be appreciated

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ezequiel•1,250
    @3eze3
    Posted about 2 years ago

    Hi Biruk Moges, very good job with this project, look I have some improvements that you can consider for your code, I hope you find them useful. never stop practicing.

    Html:

    • The h1 tag , there should only be one per html document , then you could opt to use an h2, you can't have two h1 tags in the same document.

    • It would be better to use semantic tags, for example instead of putting <div class="main" id="main"> you can use a main tag ``` <main class="card">````.

    • You should also use more descriptive names, or use a class methodology, it is more descriptive and helps not to repeat styles, there are many methodologies, but the most friendly to start with is Bem.

    Here you have the documentation in case you are interested: BEM DOC

    • You could choose to use radio type inputs, instead of buttons.

    • As for the images you can use the attribute aria-hidden="true", to avoid accessibility problems if the images are for decoration or do not provide anything more than design.

    JavaScript :

    • It would be better to use the switch event with the input tags I told you about in HTML, so you can control when the user switches to another rating.

    • And you can use the event delegation to check which input has been clicked, this helps a lot since you only use one event in the project.

    • And also with the change of event, you do not have the problem of design that at the moment of clicking in another part of the page your button is deselected, for that reason it would be better option the input. Puede consultar la información sobre la delegación de actos aquí: Event Delegation

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