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

Order Summary Component

Carisa Elam•100
@carisaelam
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?

I attempted to use what I learned about HTML structure from previous challenges to make this one a bit better. I used the mobile-first technique starting from a screen width of 320px. Before submitting my design, I adjusted the screen resolution and font-size on my computer to check for accessibility and readability across the different screen sizes in devtools.

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

I wasn't sure what to do about the background image svg. I'm not familiar with svg, so I just treated it as a regular image and changed the background color alongside it to match the design jpg the best I could.

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

Is there a better, more complete way to check for accessibility on top of what I already talked about doing? To adjust my font-size, I did System Settings > Displays > Larger Text, went with the largest option, and then viewed my design in my normal browser AND through responsive design in devtools. I also looked at the live page on my phone. Everything obviously looked fine on my end, but I worry that I am missing something by not checking a certain setting.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,720
    @markuslewin
    Posted over 1 year ago

    Sounds like a great process!

    I like to also browse through the page with a screenreader to make sure buttons and images are announced correctly. Screenreaders have lots of key shortcuts for navigation, but I find just using tab and the arrow keys eliminates a lot of guesswork regarding the HTML. I'm on Windows, so I use NVDA.

    Lighthouse inside Chrome DevTools can catch some accessibility issues as well! It usually complains about color contrast.

    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