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

NFT Preview Card Component Challenge

Balogun Murtadho•10
@Cashkid500
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey everyone! I've just completed the "NFT preview card component" challenge. Any feedback and suggestions on how I can improve are very welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted over 3 years ago

    hello @Cashkid500 ,

    In this challenge the interactive element is <a>

    <h1 class=""><a href="#">Equilibrium #3429</a></h1>

    hopefully this feedback helps.

    Marked as helpful
  • Naveen Gumaste•10,420
    @NaveenGumaste
    Posted over 3 years ago

    Hay ! Balogun Good Job on challenge

    These below mentioned tricks will help you remove any Accessibility Issues

    -> Add Main tag after body <main class="container"></main>

    -> Just use vercel or netlify and connect them using your github and boom its done Check this video it will tell you how to host

    -> Learn more on accessibility issues

    If this comment helps you then pls mark it as helpful!

    Have a good day and keep coding 👍!

    Marked as helpful
  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted over 3 years ago

    Hello @Cashkid500 ,

    I have some suggestions regarding your solution:

    To tackle the accessibility issues:

    • There should be two landmark components as children of the body element - a main (which will be the NFT card ) and a footer (which will be the attribution).<Footer> should be in the <main >read more about A simplified web page, might look something like this:

    • Anything with a hover style in a design means it's interactive. you need to add an interactive element around the Equilibrium #3429.

    • For any decorative images, each img tag should have empty alt="" andaria-hidden="true"attributes to make all web assistive technologies such as screen reader ignore those images in alt="clock icon" , alt="ethereum icon" alt="icon view"

    • the link should be wrapping the original image and either have Sr-only text, an aria-label or alt text that says where that link takes you.

    • The avatar's alt text shouldn't be alt="avatar image You can use Jules Wyvern as an alt text.

    • You can read more about alt text

    • don't use span for meaningful content.

    • You can use an unordered list <ul> for <div class="nft-info">and in each <li>, there would be <img> and<p>(for the text ).

    • You can use border-top to the class="nft-footer" instead of <hr/>.

    • It would be better

     <p>Creation of<a class="nft-owner" href="#">Jules Wyvern</a></p> 
    
    
    • never usepxfor font-size.

    • You should use em and rem units .Both em and rem are flexible, scalable units.. Using px won't allow the user to control the font size based on their needs.

    • Use max-width:350px instead of width for the card .That will let it shrink a little when it needs to

    • you can provide the link of the live solution.

    Overall , your solution is good ,Hopefully this feedback helps.

    Marked as helpful
  • IRVINE MESA•1,835
    @DrMESAZIM
    Posted over 3 years ago

    @Cashkid500 I will record a short video of me publishing my static site on GitHub .therefore please send me your email address or WhatsApp number to receive the video.

  • IRVINE MESA•1,835
    @DrMESAZIM
    Posted over 3 years ago

    hi @Cashkid500. I would love firstly for you to change the file name from nft.html to index.html Secondly If you are unaware of how to publish static live site for free on GitHub, let me know and I can help you

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

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