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

Cypto Tab

sass/scss, accessibility
Tertsegha Kpughur-Tule Moses•210
@Mosestule2003
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please I would love any feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Okafor Raphael•240
    @OkaforRaph
    Posted almost 3 years ago

    Hey Moses, congratulations on completing the challenge! You did a great job 😉

    Let me give you some little tips for optimizing your code:

    • First, for semantic HTML, the section tag is expected to wrap the div and not the other way round.

    • Always make use of relative unit of measurement like "rem" instead of "px".

    Hope this help! Happy coding 😁

  • Rohit Kumar Saini•270
    @rockingrohit9639
    Posted almost 3 years ago

    Hey, @Mosestule2003 Congratulations on your submission.

    I looked at your design and found that it could be improved more. The things which you can improve are --

    • Use the font-size of paragraph to be 18px and don't have any <br> in your <p>. It will automatically fit with the container width.
    • The color of the paragraph also does not match, you can change it too.
    • You should have all the content in <main> and you should also have <footer>. So your report will not be having any issues.
    • Add <!DOCTYPE html> at the top of your HTML document.
    • You should have width: 100% in the CSS not at the direct element.
    • You should not have <p> inside H3 or any other heading element, instead you can use <span>.

    I hope this feedback will help you a little bit in improving your design. All the best.

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