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

Responsive Rating Component with HTML/CSS/JS

Priya Aggarwal•160
@pa-aggarwal
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first challenge working with JavaScript that I haven't used in a while! Thank you for any feedback :)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted about 3 years ago

    Heyo,

    It looks great! It's nice you did this with inputs and even paid attention not letting people submit empty ratings. ^^ There's a few small things you could do here to improve:

    1. You can remove the action attribute from the form, it's not really needed here. Instead of the div named "ratings" inside this form, you could use <fieldset> to group together the inputs. You could also add a screen reader only <legend> to this with a title of "Ratings", just to make the form super clear.

    2. Instead of the <section> named "content" you could use <main>, so your solution has a landmark at least (this will get rid of the accessibility issues in the report, too).

    3. display: none isn't an accessible way to hide your inputs, as this will hide them from screen readers as well, which isn't something you wanna do. You can find some tips on how to solve this in this article.

    Marked as helpful
  • Shashree Samuel•8,860
    @shashreesamuel
    Posted about 3 years ago

    Hey good job completing this challenge

    Keep up the good work

    Your solution looks great however I have some feedback on your accessibility and validation issue

    • Document needs to have a main landmark, this is caused by the inability to identify the main content and hence to fix this you can use the semantic main tag which when wrapped with all the tags between the body element will resolve this error since it establishes a main content.

    Once this issue is resolved then the rest of your accessibility issues should be resolved

    In terms of your validation error, the attribute action on the form element cannot be empty since the form needs to redirect to another page etc in order to process or output the data stored.

    Also I would not recommend using the div tag instead of the section tag since it i I hope this helps

    Cheers

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