Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 13 days ago

HTML CSS SCSS Javascript Mobile firts bem

accessibility, bem, sass/scss
P
RF13•590
@rf1303
A solution to the Body Mass Index calculator 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?

I am proud to have completed a functional and visually appealing project that allows users to calculate BMI in both metric and imperial systems. I implemented accurate conversions between feet/inches and stones/pounds, and also included custom messages for the user to understand their result and healthy weight range.

What I would do differently next time is to organize the JavaScript code better from the beginning, using reusable functions and separating logic from presentation. I would also spend more time planning and testing the accessibility of the HTML from the beginning, as catching problems like missing landmarks or missing aria labels at the end can lead to redoing parts of the structure. I would also automate some of the flow with more consistent validations and keyboard tests.

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

The biggest challenges were the grid and the changes to the bmi limits and the changes to imperial and metric, finding and testing what looked best, and finding the way to calculate the bmi.

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

It would be in the HTML accessibility part and in the Javascript code structure and if the css code looks good.

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 RF13'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, SASS, 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.