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

Order summary component challenge hub

accessibility
Maria Castillo Berto•80
@MariAleCas
A solution to the Order summary 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

  • Elena Martinez•80
    @nenamartinez
    Posted over 3 years ago

    Hi there! I'm more experienced as a designer than coder so I'll be focusing on that in my feedback.

    -Spacing issues. There should be more space under the paragraph and more space between the "proceed to payment" button and 'cancel order' part. Also, the spacing inside the "annual plan" box is not right. The music icon should be more left, 'annual plan' info as well, and the 'change' should be more to the right.

    -Overall sizing. Because the vertical spacing above isn't enough, the card looks too wide compared to the design.

    -Color issues. The heading text should be dark blue, not black. The 'annual plan' text should be bold and dark blue, also.

    -No hover state. The design is supposed to have hover states on the 'Proceed to payment' button and the other links. I don't see any hover state change on the site preview. 'Cancel order' doesn't seem to be a link.

    Also, I cannot view your code with the link above. The link seems to be broken. If you want to get more feedback on the code specifics, please try to fix the link so your code will be visible to everyone. Keep on coding! I'm new to it all, too.

    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