Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Order Summary challenge

bem, accessibility
Cedricโ€ข130
@NexusLo
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

๐Ÿ‘‹ Hi everyone! This is my solution for the order-summary challenge, nothing to be very pride of here but practice make perfect as they say

What challenges did you encounter, and how did you overcome them?

๐Ÿ‹๏ธ Not any challenge encoutered, my objective this time was to complete the challegnge as fast as I could

What specific areas of your project would you like help with?

โœ๏ธ As usual If you notice anything please feel free to give out your tips

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bryan Liโ€ข3,530
    @Zy8712
    Posted about 1 year ago

    Hi there! Your site looks pretty good, nice work!

    Some things I noticed when testing your site:

    • for certain screen sizes the background doesn't extend to fit the full size of the screen, this may be due to how you implemented your css for your site
    • I would suggest making sure your "wrapper" class has a width of 100vw so that it extends the full size of the screen
    • for the background image you can use background-size: cover; so it fits the full background
    • one other thing would be to use more semantic tags such as <main> instead of having all divs. This is for accessibility purposes

    Hope you find this feedback useful ๐Ÿ‘

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