Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Flexbox solution

Antony Daniel Ocegueda Ruelas•210
@Antonator
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I did the best I could, my solution is with flexbox and media queries, I think the result is good. Any feedback is welcome :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Antony!

    👍Good job on completing this challenge!

    I hay some feedback on this solution:

    • The card is almost has full width on mobile view (360px * 640px). Try to add padding on your body element.
    • I noticed that the HTML lang attribute has value es, which is Español based on what I see on MDN about lang attribute. The problem is that, the current page has English language not Spanish. So, I recommend to keep value of the lang attribute with en.
    • The Proceed Payment should have bolder font weight.
    • For any decorative images, which in this case, all images are decorations only. You should leave the alt="" empty and add aria-hidden="true" or role="presentation", to make sure all screen readers ignore those images.
    • Also the alt (Alternative text) should not be hyphenated. It should be descriptive for human to read.
    • Order Summary should be a heading tag. It is the title of the card.
    • You should wrap all your page content with main tag. I'm not sure why Frontend Mentor doesn't report any accessibility issues.
    • Are trying to make all elements set to box-sizing: border-box? If so, you should add box-sizing property to the html element.
    *, *:after, *:before{
        box-sizing: inherit;
    }
    
    html {
      box-sizing: border-box;
    }
    
    • You should never change the root font size. I recommend to keep the default behavior to make sure that every device and browser will render the size correctly.
    • The body font size should also use rem unit.

    That's it! Hopefully this is 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