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

Order Summary Component Challenge

Raitis•190
@RaitisVilums
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I just started and it's my first try of making something. I will be happy to receive feedback on my solution.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! Raitis,

    To solve accessibility issues:

    1. wrap everything in your body in <main> OR give role="" to the direct children of your <body> ... Click here to read more here

    2. Don't let alt attribute empty, always add some meaning text in it, so that user able to understand.

    3. In order to center your background image use background-size: contain;

    in your below code

    body {
        background-image: url("./images/pattern-background-desktop.svg");
        background-color: hsl(225, 100%, 94%);
        background-repeat: no-repeat;
        background-size: contain; /* HERE I ADDED JUST UPDATE IT IN YOUR MAIN CODE*/
        font-size: 16px;
        font-family: 'Red Hat Display', sans-serif;
    }
    
    1. Change your code
    <div class="attribution">
            Challenge by <a href="https://www.frontendmentor.io?ref=challenge" target="_blank">Frontend Mentor</a>.
            Coded by <a href="https://www.frontendmentor.io/profile/RaitisVilums" target="_blank">Raitis Vilums</a>.
        </div>
    

    TO

    <footer class="attribution">
            Challenge by <a href="https://www.frontendmentor.io?ref=challenge" target="_blank">Frontend Mentor</a>.
            Coded by <a href="https://www.frontendmentor.io/profile/RaitisVilums" target="_blank">Raitis Vilums</a>.
        </footer>
    

    There are so many changes are required, as If I enter all then this comment will become so longer. So do what @Madmanden said above. and Rest things I wrote.

    I hope you understand.

    Good Luck ;)

    Marked as helpful
  • Christian Holm•500
    @Madmanden
    Posted over 3 years ago

    Hi Raitis! Good effort 😊 On my phone it isn’t centered though. And the box-shadow is too dark.

    Marked as helpful
  • Sam Guliker•540
    @Sam-Guliker
    Posted over 3 years ago

    Hi Raitis,

    For your first time you did a great job. There are a couple of things you can pay attention towards to.

    • Check your headings: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements
    • For images use an alt type: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img
    • Try to use landmarks like: Header, Main, and Footer. https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/navigation_role
    • You can remove the border-radius top on the mid section.

    I hope this was helpfull,

    Happy coding

    Marked as helpful
  • Raitis•190
    @RaitisVilums
    Posted over 3 years ago

    So when I uploaded the solution, it all went wrong, how can I fix this?

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub