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

Age Calculator built with Bem, SASS/SCSS, Javascript and Vite

accessibility, bem, sass/scss, vite
Johnny•490
@johnnysedh3lllo
A solution to the Age calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The Javascript was so much fun to write. Well, mainly the algorithm.

  • what do you guys think of my code?
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

    Congratulations on completing the Age Calculator App project! Your project shows a great combination of HTML, CSS, and JavaScript skills. Here are some best practices to consider for further improvement:

    • Semantic HTML: Good job on using semantic tags like <article> and <form>. Ensure to use semantic elements wherever possible for better accessibility and SEO. More on semantic HTML can be found here.

    • CSS Best Practices: Your CSS is well-structured. Consider using a consistent naming convention like BEM for CSS classes to improve readability and maintainability. Learn about BEM here.

    • JavaScript Validation: It's great that you've implemented custom validation. Enhance this by providing real-time feedback as the user types, rather than on form submission only. More on form validation here.

    • Responsive Design: Ensure that the app is fully responsive on various devices. Test across different screen sizes and make necessary adjustments using media queries. More on responsive design here.

    • Accessibility: Focus on making your website accessible. This includes proper use of ARIA roles and ensuring that all interactive elements are keyboard accessible. More about web accessibility can be found here.

    • Performance Optimization: Optimize your application for performance, especially if you plan to scale it up. This includes optimizing images, minifying CSS and JavaScript files, and reducing HTTP requests. More on web performance here.

    Great work on this project! Your dedication to learning and applying web development concepts is commendable. Keep exploring and experimenting with new ideas and technologies to further enhance your skills.

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