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

Interactive rating component

accessibility
Zahra Abellou•370
@zahraabellu
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kamran Kiani•2,780
    @kaamiik
    Posted 6 months ago

    سلام. تبریک میگم بابت انجام این پروژه! کارتون خوبه، ولی چند نکته هست که می‌تونن به بهبود کدتون کمک کنن. نکات رو به انگلیسی مینویسم تا دقیق‌تر بیان بشن:


    HTML Structure

    • Form Structure: The structure of your HTML is crucial for this challenge. You should wrap the question and numbers inside a <form> tag, which includes a submit button. This ensures proper functionality and accessibility.
    • Fieldset and Legend: To group the question and numbers semantically, use <fieldset> and <legend>. The question can be placed inside the <legend> tag. This improves accessibility and structure. You can learn more about these elements on MDN.
    • Radio Buttons and Labels: The numbers should be a group of radio buttons, each with a corresponding <label>. This makes the interface more user-friendly and accessible. The current button implementation is incorrect and should be replaced.

    Accessibility and Images

    • Decorative Images: For decorative images, the alt attribute should be empty (alt=""). This ensures screen readers skip over them, improving accessibility.

    Fonts and Styling

    • Font Importing: It’s recommended to host fonts locally or include them directly in your HTML. The current method of importing fonts isn’t ideal for performance and reliability.
    • CSS Reset: Consider using a CSS reset at the beginning of your stylesheet. Both Andy Bell and Josh Comeau provide excellent CSS resets, which you can easily find online. This helps ensure consistent styling across different browsers.

    Layout and Sizing

    • Text Container Sizing: The use of width: 25rem; and height: 24rem; for text containers is incorrect. Instead, use max-width with rem units to allow the content to flow naturally while maintaining a reasonable maximum size.
    • Button Sizing: For buttons, avoid fixed dimensions like width: 50px; height: 50px;. Instead, use padding to control the size, which makes the button more flexible and responsive.
    • General Width Usage: All instances of fixed width in your code are unnecessary. Replace them with max-width where needed, using rem units for better scalability.

    Final Suggestion

    I strongly recommend refactoring the code based on these suggestions before moving on to the next challenge. This will help you build a stronger foundation and improve the overall quality of your work.

    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

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