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

Just some html and css

Thanos Balogiannis•50
@thanosballo
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Greetings to all

heres my solution.

Still in need for some modifications ,but pretty much thats it .

Cheers !

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hi There! 👋

    Congratulations on finishing this challenge! 👏

    @dewslyse has given some incredible feedback for you. Here is some feedback from me:

    • Accessibility
      • For any decorative images, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images. In this case, all icons and images are decorative only.
      • Next time, if you write alternative text for images, it should not be hyphenated. The user of assistive technology relies on alternative text to know the image content. So, it's recommended to make it human-readable and informative.
      • Create a custom :focus-visible styling to any interactive elements (button, links, input, textarea). This will make the users can navigate this website using keyboard (by using Tab key) easily.
    • Styling
      • To make all the elements box-sizing: border-box do the following.
    html {
      box-sizing: border-box;
    }
    
    *,
    *::after,
    *::before {
      box-sizing: inherit;
    }
    
    • I would recommend changing the width: 375px to max-width: 23.5rem. Currently there's a horizontal scrollbar on my mobile view (360px * 640px).
    • Also, I would recommend adding some padding on the body element to prevent the card from touching the browser edges.
    • Always use classes to reference all the elements that you want to style. Using id is going to make your stylesheet have high specificity (hard to maintain).

    That's it! Happy coding! 😁

    Marked as helpful
  • dewslyse•3,005
    @dewslyse
    Posted over 3 years ago

    Hello @thanosballo, congrats on your submission. Well implemented. Some things to note:

    • Remember to include landmarks (e.g. header, main, footer etc) in your markup. In this case you could change <div class="container"> to <main class="container">.
    • Make sure headings increase by one. You could change <h4>Annual Plan</h4> to <h2>Annual Plan</h2>
    • The order summary component is missing the background image

    Happy coding!!

    Marked as helpful
  • Dev Rathore•2,540
    @GitHub-dev12345
    Posted over 3 years ago

    Reduce the accessibility changed this code:

    1.<div class="container"> to <main class="container">

    this code usefull for you, click on the marked as helpful

  • Dev Rathore•2,540
    @GitHub-dev12345
    Posted over 3 years ago

    used this CSS Property in your card to increase and decrease the size of card:

    1.In Card design CSS Code Used this:

    transform : scale(0.8); this property decrease the size of card. 😉

    large size for increase the number of scale & small size for decrease the number of scale

    And used this code for background image : In body tag used this CSS property: body{ background : url("./images/uesd image path") no-repeat; background position: top center; background size: 100% 50%; ( this is your choice check the image performance, and the gave the size percentage on your choice); this code very helpful for your background image😉😎 keep it up; } this code helpful for you, plz click on the mark the 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 1st-party linked stylesheets, and styles within <style> tags.

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.

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