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

Order Summary Challenge using CSS advanced Properties and selectors.

accessibility
JAILBREAK•60
@JAILBREAK-101
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first FrontEnd Challenge Project that was submitted, please review and get back to me, on what needs to be changed, updated, or deleted. Thank you as you do so. I didn't have any areas of difficulty in this project, instead i learnt new Advanced CSS properties such as the :is() selector, and also making use of the nth-of-type() and nth-child selectors for my CSS. I was also able to write Semantic HTML that makes meaning, not only to me, but to screen readers, for accessibility purposes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted over 2 years ago

    Hi there 👋:

    • We gladly welcome you to the Front end mentor community
    • You just completed a solution as per the design Congratulations..🙌
    • But, There's an report in accessibility which causes accessibility error

    RESOLVING THE ERROR

    • The div with class attribution is meant to be a footer element
    • Because using semantical elements to structure the HTML improves the accessibility for screen readers
    • So change the div into footer element

    MESSAGE:

    • If my answer helps you then providing an upvote will be very helpfull
    • And don't forget to mark this comment as helpfull. If it helps to resolve your issues
    • I hope you learned a lot of stuffs during this project, Congrats JAILBREAK

    GREETINGS:

    • Happy coding..🙌
    • Peace be upon you with god's mercy & blessings..✨

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