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

Tip calculator app using HTML, CSS and Javascript

accessibility
P
Aydan•680
@AydanKara
A solution to the Tip 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?

💡 Proud of:

  • I wrote clean, reusable, and well-structured JavaScript by implementing DRY (Don't Repeat Yourself) principles and using pure functions.
  • Improved accessibility by using semantic HTML and ensuring error messages are properly displayed.
  • Made the UI responsive and WCAG-compliant, ensuring it works well on mobile and desktop devices.

🔄 Next time, I would:

  • Consider using a state management approach (e.g., an object to track all input values) for better scalability.
  • Implement unit tests to ensure calculation functions work correctly in all cases.
  • Explore CSS animations to enhance user experience when showing/hiding error messages.
What challenges did you encounter, and how did you overcome them?

❌ Challenges:

  • Handling cases where people input is 0 (which causes division errors).
  • Ensuring reset button is disabled when there’s no valid input.
  • Positioning and styling SVG icons inside inputs for better UI/UX.

✅ How I solved them:

  • Created a validation function (validatePeopleInput()) that prevents calculations if the input is invalid.
  • Centralized logic for enabling/disabling the reset button.
  • Used CSS flexbox & absolute positioning to properly align icons inside input fields.
What specific areas of your project would you like help with?

🔍 Possible improvements/questions:

  • Is there a more efficient way to handle state updates? (e.g., using an object instead of multiple variables)
  • Would it be beneficial to add local storage to remember user preferences (e.g., last tip percentage used)?
  • How could we further optimize accessibility to ensure screen readers interpret the form elements correctly?

Would love any feedback on how to further refine and optimize the project! 🚀

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