Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Age calculator app Solution

accessibility, animation, react, tailwind-css, node
Alok Suman•2,360
@Alokray007
A solution to the Age calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


🛸 Hello Front-End Mentor Community! I'm Alok and this is my solution 😊

🛠️ Built with:

HTML 🧾 Tailwind 👾 React 🤖 BEM Notation 🅱️ Mobile first workflow approach 📲 This project was a good challenge in many aspects. Each input needed date validation and I didn't know how to do some of them, so I had to learn them while doing it. Although Javascript has been a bit more challenging on these last few projects.

An excellent challenge to practice many different skills at once! 😊

Thanks to the Front-End Mentor team that create challenges that make us learn a lot from doing them. 💟

If you have any suggestions on how I can improve this project, feel free to leave me a comment!

Feedback welcome 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    This project needs a lot of fixes.

    • Missed background colour
    • Missed inputs label color
    • Input validation ( you can write text if you want )
    • No components used for React ( you should use more components and not only App.jsx file)
    • This project is not responsive for mobile devices!. (Checked for iPhone 12 Pro and newer)

    Overall you should recheck this project, but you are in the right way!

  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted over 1 year ago

    @Alokray007

    My guy just copied my solution text and didn't even bother to change a single word except for the name and React 😅

  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    This needs some markup changes to be accessible

    1. Use a fieldset and visually-hidden legend to wrap the 3 inputs
    2. The fields should be programmatically linked to the error wrappers. Give the paragraphs wrapping the errors a unique ID and an aria-live attribute. Then give the input an aria-desciribedby its error wrappers ID.
    3. Give the page a visually-hidden h1 and the result section a visually hidden h2.

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub