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

Order Summary Page

accessibility, bem, lighthouse
Chitrang•150
@cwebdev
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi,

This is my first time using CSS custom properties. I am planning to use it more in future. Any feedback regarding that is welcome.

Any other general feedback is also welcome. Happy Coding!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alexander Lippitsch•120
    @LipAlex1
    Posted over 3 years ago

    Hi Chitrang,

    you may want to look at the report as there are ally issues. Make sure you use semantic html (main, header, nav, section, aside, footer etc.). Assigning classes to main, header and footer tags is redundant code as these tags are meant to be used non-repetetively.

    Also, make sure you use ONE h1 tag since this is important for SEO reasons and it's the quasi standard in webdev.

    The background doesn't look like the specs. There is more work to be done on background image and background-colors to get it to look right.

    The site is not fully responsive particularly because there are no breakpoints in the design and the font-sizes are set to fixed widths that hurt the design on smaller viewport widths.

    Designing the entire HTML structure with divs only is considered bad style but not necessarily wrong. Semantic tags as well as button, input and list tags would make that code leaner, faster and easier to maintain. Commenting the code is doing yourself a favor as it saves you time when revisting the code.

    Keep up the good work and happy coding!

    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

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