Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
2
Comments
1

Tami Ribeiro

@tamiribeiroSão Paulo, SP40 points

Analysis and Systems Development college student | Front-end enthusiastic.

I’m currently learning...

HTML | CSS | JavaScript. // Curious about ReactJS

Latest solutions

  • Order summary component | HTML | CSS


    Tami Ribeiro•40
    Submitted over 3 years ago

    1 comment
  • nft preview card component


    Tami Ribeiro•40
    Submitted over 3 years ago

    2 comments

Latest comments

  • José Manuel Esperanza•220
    @JoseAngara
    Submitted over 3 years ago

    Order summary with HTML & CSS

    1
    Tami Ribeiro•40
    @tamiribeiro
    Posted over 3 years ago

    Hello there! Nice work done here. I think I can give you some tips about HTML tags tho. Thinking about better accessibility, all your content (everything that's inside your <container>) should be also inside a <main> tag. Besides that <article> it's not the better option here. A <article> tag specifies independent, self-contained content, and since everything is a simple card, maybe a <div> with a class would be more semantic. Here's something that might make it easier to understand: https://www.w3schools.com/tags/tag_article.asp. Your page also should have a level-one heading, so <h1>Order Summary</h1>. And I think your attribution would be more semantic inside a <footer> tag 😊

    Marked as helpful
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

Beta Member

This badge is a shoutout to the early members of our community. They've been around since the early days, putting up with (and reporting!) bugs and adjusting to big UX overhauls!

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

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