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

HTML,CSS image overlay and position property

accessibility
jill pandya•90
@jillpandya2594
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


All suggestions are welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Travolgi 🍕•31,320
    @denielden
    Posted about 3 years ago

    Hi Jill, great work on this challenge! 😉

    Here are a few tips for improve your code:

    • add main tag and wrap the card for improve the Accessibility
    • using <hr> for the line is not the best way because this tag have a semantic meaning... in this case use div with border-bottom because this line is decorative
    • remove margin-top from card class because with flex they are superfluous
    • add min-height: 100vh to container class because Flexbox aligns child items to the size of the parent container
    • add transition also on the text with hover effect

    Overall you did well 😁 Hope this help!

    Marked as helpful
  • NitheeshKumar C•440
    @NitheeshKumar-C
    Posted about 3 years ago

    Hi there😃,

    The solution looks good. Here are some improvement code,

    For more accurate center use flex-box:

    Based on the problem use :

    body {
        min-height: 100vh;
        display: flex;
        justify-content: center;
        flex-direction: column;
    }
    

    For <hr> (Horizontal line):

    hr {
        border: 1px solid;
    }
    

    Happy Coding👨‍💻,

    NitheeshKumar

    Marked as helpful
  • patil sahil•440
    @Patilsahil821
    Posted about 3 years ago

    hey, awesome you did it very perfect the only thing you have to look that is accessibility issues and html issues except these you did very well and Don't forget to check mine projects also. best of luck for your next projects.....

    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 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

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