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

Mortgage Repayment Calculator with html, css and javascript.

AyanfeoluwanimiSeriki•110
@AyanfeoluwanimiSeriki
A solution to the Mortgage repayment 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 happy because the calculator works accurately and the interface is user-friendly, which adds significant value. Implementing features that guide users when they make mistakes shows attention to detail, and if it works well on different devices, that’s a great achievement!

Ensuring my code is modular and well-commented can help with future maintenance or upgrades. I should strive to be faster and use shortcuts in my code instead of long methods.

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

Ensuring that user inputs were valid and providing appropriate error messages when they weren't, making sure the calculator looked good and functioned well on different devices and screen sizes, managing the visibility of error messages, and resetting them when inputs changed, as well as adding interactive elements like shake effects for invalid inputs and color changes for selected mortgage types, all contributed to enhancing both the functionality and user experience of the mortgage calculator.

Each obstacle provided an opportunity to improve my coding skills and attention to detail, and I successfully overcame them all.

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

Improving the validation logic to ensure all edge cases are covered, such as handling special characters or extremely large numbers.

Making the interface more visually appealing and user-friendly, perhaps with better color schemes, typography, or layout adjustments.

Ensuring that the calculator works seamlessly on various devices and screen sizes.

Ensuring the application is accessible to all users, including those with disabilities. This could include adding keyboard navigation, screen reader support, and color contrast enhancements.

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 AyanfeoluwanimiSeriki'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.