Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

INTERACTIVE RATING COMPONENT๐Ÿš€

Guerinik Abderrahmaneโ€ข460
@AbderrahmaneGuerinik
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello community๐Ÿ‘‹

Here is another project finished

  • Responsive for tablet-desktop and mobile๐Ÿ“ฑ.

  • 99% Performance 100% SEO 92% Accessibility

  • Your feedback can really help me!

Enjoy coding!๐Ÿ‘จโ€๐Ÿ’ปโœจ

Code
Couldnโ€™t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kasโ€ข7,655
    @FluffyKas
    Posted over 1 year ago

    Heyo,

    Looks like a really good solution! One thing you could do is to disable the submit button until the user chooses a rating to prevent empty submissions. Few tips to improve on accessibility:

    • They best solution for this sort of rating system is radio buttons. The function of a list of regular buttons may not be immediately obvious for someone who doesn't rely on visuals to use the internet (e.g. ppl using screen readers). To achieve this, you can visually hide the radio buttons and display their labels as the clickable "buttons". Plus, this makes handling the JS bit much easier too. Probably you won't rework the challenge, but I thought it's something you might wanna keep in mind the next time you face a problem like this.
    • Although this is just a component, it's generally a good idea to wrap all your content in at least a <main> tag.
    • For decorative images, you should leave the alt text blank (the star icon and the little image on the thank you page could be both considered decorative images).

    Well done :)

    Marked as helpful

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