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

HTML5, CSS, Framework Tailwind CSS, Javascript Vanilla, Google Fonts

accessibility
Marcone Silva de Brito•80
@marconesdb
A solution to the Age calculator app 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?

Estou particularmente satisfeito com a validação dos dados de entrada. O sistema consegue identificar rapidamente entradas inválidas, como dias ou meses fora do intervalo válido, além de lidar com anos fora do intervalo permitido. Na próxima vez, eu provavelmente modularizaria o código JavaScript, separando funções de validação, cálculo de idade e manipulação do DOM em arquivos ou funções independentes, visando maior escalabilidade e manutenção.

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

Lidar com diferentes formatos de datas e garantir que todos os cenários (anos bissextos, meses com 30 ou 31 dias) fossem cobertos exigiu um esforço extra. O uso de condicionais e controle de erros ajudou a superar esses desafios. Garantir que a aplicação funcionasse adequadamente em dispositivos móveis foi um desafio. A utilização de Tailwind CSS e @media queries foi essencial para ajustar o layout.

What specific areas of your project would you like help with?
  1. Melhorias na acessibilidade: Apesar de a interface estar funcional, a otimização para leitores de tela e outras ferramentas de acessibilidade pode ser aprimorada.
  2. Otimização do cálculo de idade: Gostaria de explorar métodos mais eficientes para calcular a idade, talvez utilizando bibliotecas como Moment.js ou Date-fns, que possuem funções específicas para lidar com datas.
  3. Responsividade. Melhorar a responsividade para dispositivos móveis.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Marcone Silva de Brito'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.