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

NFT Responsive Project

accessibility
tomatas95•50
@tomatas95
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had a hard time getting the photo hover to work :/

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pradeep Saini•990
    @pradeeps4ini
    Posted almost 3 years ago

    Hi, @tomatas95. Well done on completing your first project.

    Your live project doesn't load, because of some misconfiguation. Please follow the advice of @correlucas to rectify that.

    • You should wrap the main content (card) in a <main> element. Using semantic elements is better for accessibility and make the code ease to read. You use <article> when you want to wrap content which doesn't need context of other content on the page and can be reused somewhere else. So, don't nest <article> with in <article>.

    • For the image hover effect, i wrote this small demo code. You can modify and learn from it. https://codepen.io/pradeeps4ini/pen/yLKbRqB

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Hello Tomatas, Welcome to the Frontend Mentor community and congratulations for your first challenge:

    I'll give you some tips as I see is your first time applying for a challenge:

    Your solution live site isn't displaying due a problem of configuration in Github Pages, isn`t? You can consider use Vercel or Netlify that are websites that let you connect your Github accounts and repositories. I recommend vercel.com because its easier to use and you'll get your solution page online in a matter of minutes.

    Since I cannot see your live page, I cannot help you much about the solution and the hover issue. I did this challenge too and an article from W3 Schools helped me a lots to understand how this kind of complex hover-image-icon works. Link below:

    https://www.w3schools.com/howto/howto_css_image_overlay_icon.asp\

    If you want to see how I've applied these W3 Schools concepts for image icon hover, you can check my solution:

    https://www.frontendmentor.io/solutions/nft-preview-card-vanilla-css-custom-design-and-hover-effects-b8D1k9PDmX

    One time you've your site live, just update your solution and also the screenshot, this way you can compare your solution to the design file. Using the slider in the challenge HUB.

    Feel free to do me further questions, I'll be happy to help you!

  • tomatas95•50
    @tomatas95
    Posted almost 3 years ago

    thank you for checking my code! I''ll try my best to fix all mistakes youve all pointed out, the overlay thingy has gotten much more easier to understand thanks to the examples given!

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