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

Cartão Interativo Responsivo com HTML, CSS e JavaScript

accessibility, animation, pure-css
Nathy•30
@Sonaite
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?

Me orgulho muito do design final do projeto e de conseguir fazer o cartão funcionar de forma dinâmica, mostrando as informações conforme o usuário digita. Foi minha primeira experiência criando um layout interativo com HTML, CSS e JavaScript.

Na próxima vez, eu dedicaria mais tempo a organizar melhor meu código, para que ele fique mais limpo e fácil de entender. Também quero aprender a escrever funções mais eficientes e usar boas práticas, como separar melhor a lógica da apresentação.

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

Um dos principais desafios que enfrentei foi tornar o layout totalmente adaptável utilizando media queries. Embora tenha conseguido fazer o design funcionar bem em vários tamanhos de tela, percebo que em alguns dispositivos móveis, especialmente quando usados na posição horizontal (deitados), o cartão pode não estar perfeitamente ajustado.

Para tentar superar essa dificuldade, estudei as melhores práticas para media queries, testei em diferentes resoluções e dispositivos, e fiz ajustes progressivos. Ainda assim, reconheço que essa é uma área onde posso melhorar e pretendo aprofundar meus conhecimentos para garantir uma experiência consistente em todas as telas.

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

Ainda estou aprendendo e não tenho muito conhecimento técnico, por isso gostaria de receber feedback sobre as partes do meu código que posso melhorar. Quero entender melhor quais práticas são mais recomendadas e como deixar meu código mais organizado e eficiente.

Também gostaria de dicas para aprimorar a responsividade e a validação do formulário, para garantir que meu projeto funcione bem em diferentes dispositivos e situações.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•4,610
    @thisisharsh7
    Posted about 2 months ago

    Great job on implementing an interactive credit card form! 🎉 That's a solid first step into JavaScript and responsive design.

    Highlights:

    • ✅ Clear layout and structure using semantic HTML.
    • ✅ Real-time card updates enhance user experience.
    • ✅ Use of media queries to adapt layout on different screens.

    Suggestions:

    1. Code Organization:

      • Use more descriptive id/class names (inunber → card-number).
      • Separate logic from presentation: consider adding a separate JS file (script.js) and placing styles in style.css.
    2. Form Validation:

      • Add JavaScript validation for number fields to avoid non-numeric input using input type="text" + regex or type="number" where appropriate.
      • Use pattern attribute in HTML to define allowed formats (e.g., pattern="\d{4} \d{4} \d{4} \d{4}" for card number).
    3. Responsiveness:

      • Improve mobile landscape layout: ensure consistent spacing and alignment.
      • Use flex-wrap and gap for better scalability.
    4. Accessibility:

      • Add aria-labels for better screen reader support.
      • Use <fieldset> and <legend> for grouping form elements semantically.

    Keep going! You're off to a great start. 🚀

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