Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Interactive rating component using flexbox

accessibility, lighthouse
saccoViola•90
@saccoViola
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?

I tried to do this projects a few months ago and it took way longer that now. I'm proud that I improved trying to focus more on accesibility

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Imre Bartis•60
    @imrebartis
    Posted 5 months ago

    README.md:

    • ATM it contains the template for writing the README. It would be helpful to rewrite it so that it gives details about the actual implementation of the challenge

    Corner cases:

    • Instead of letting the user press the submit button even if no rating has been selected e.g. an error message could be displayed telling the user that they have to select a rating number first
    • If the user clicks on several rating buttons one after the other, they all turn orange. It would be more user friendly to have only the rating button that has been most recently clicked be orange

    Does the solution include semantic HTML?

    • There are some improvements that could be made here:
      • No <main> element to identify primary content
      • Rating interface not wrapped in <form>
      • Missing ARIA labels for interactive elements
      • Content sections could use better semantic elements like <section>
      • No <header> elements for content organization

    Is it accessible, and what improvements could be made?

    • Improvements that could be made:
      • Add semantic HTML structure
      • Implement proper form controls
      • Add ARIA attributes and roles

    Does the layout look good on a range of screen sizes?

    • The design implementation is not responsive

    Is the code well-structured, readable, and reusable?

    • It could be better. Suggestions:
      • Organization:

        • Group related properties
        • Add consistent spacing
        • Use CSS custom properties
        • Add comments for sections
      • Naming Conventions:

        • Make class names descriptive
      • Variables and Reusability:

        • Create root variables
        • Define reusable values
      • Media Queries:

        • Add proper breakpoints
        • Group responsive styles

    Does the solution differ considerably from the design?

    • The styles are quite close to the desktop design
    • As mentioned before, the design implementation is not responsive, the mobile styles are missing
    • On hover the rating buttons' values should be of a darker color though (the contrast between the current grey number and its white background is not great)
    • The background of the .main-container should be gradient

    Some issues with the JS code:

    • There are duplicate event listeners (they are the culprit behind the second issue mentioned above in the Corner cases section)
    • There is no validation (that's why the user can click the submit button even if no rating value has been selected)
    • Use of inline styles
    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