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

Interactive card details Built with ReactJS + flex, grid + SASS

accessibility, react, sass/scss
Guilherme Focassio dos Santos•90
@guiklose
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi all! I'm sending another ReactJS project, this time I used SASS to improve my organization/logic of css files. It was an amazing project to learn about React (hooks, state) and SASS (itself). Feel free to read the code and give me some feedback on how I can improve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • S MD suleman•3,510
    @sulemaan7070
    Posted about 2 years ago

    hey 😄Guilherme Focassio dos Santos, congratulations on completing the challenge... here are a few tips to make your site better.

    1.limit the number of characters to 2 in the MM and YY fields and 3 in the case of CVC.

    1. Limit the number of characters to be accepted as input to 16 in case of card number.

    3.Make sure to add validation messages and change the color of the particular input field upon wrong input..

    4.Even when I enter 16 numbers in the card number input field this message is popping up.. Please, fill with your right card number. make sure to fix that

    Hope that helps you,Happy coding💯😄👍🏻

    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