Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Interactive Card Details Form using HTML, CSS and JavaScript

accessibility
Caleb Abuul•320
@Caleb-Abuul
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

During this challenge, I learnt a great deal from stackoverflow, freeCodeCamp and YouTube. As always Kelvin Powell's YouTube videos, especially on responsive layout, use of grid and flex-box, were a huge help. It took me a great deal of time to finish the challenge but at long last I was able to pull through. I am most proud of updating the card in real time as a user enters their details, and also formatting the card-number input field such that the card number appears in clusters of four-digits. Next time I will use frameworks such as tailwind-CSS, and maybe ReactJS to "make my life easier" [as Kelvin would put it]

What challenges did you encounter, and how did you overcome them?

One of the most challenging things I encounter was being able to format the card-number input field such that when a user enters the digits, a space will be inserted after every four digits. To overcome this challenge, I headed over to stackoverflow, and luckily for me, I wasn't the only one facing the issue. So, I looked at the solutions that were helpful to others, and I tried a couple. Finally, one of them worked for me. Using regular expression in JavaScript, as the solution stated, I achieved my aim. Another challenge, was updating the card details in real time as the user enters their details. Stackoverflow came to the rescue again. All I needed to do was add an eventListener that set the innerText of the output p to the value of the form input fields on input.

What specific areas of your project would you like help with?

I would like help with my JavaScript because I feel that most of the code I've written down could be shortened and made easier to read with less code by using functions to do repetitive tasks. Also, I would like help with form validation using JS - especially date and email validation.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Caleb Abuul's solution.

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.