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

Tip Calulator App

accessibility, pure-css
Muhamad Rukhul Kirom•380
@rukhulkirom
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?

I am most proud of how the Tip Calculator App turned out, especially in terms of its clean and responsive UI, efficient calculation logic, and well-implemented error handling. The app dynamically updates the tip and total amount per person while providing a smooth and interactive user experience. The inclusion of a custom tip input alongside preset percentage buttons adds flexibility, and the reset functionality ensures that users can easily start over without any hassle. However, there are a few things I would do differently next time. I would focus more on accessibility by adding aria-live regions to ensure screen readers can announce changes dynamically. Additionally, allowing decimal inputs for the number of people would improve usability for cases where users want to split a bill unevenly. Mobile optimization could be enhanced further by adjusting button layouts and spacing for smaller screens. I would also improve user feedback by making error messages more visually prominent and perhaps adding tooltips for guidance. Finally, implementing local storage to save user inputs would help retain data in case of an accidental page refresh.

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

One of the main challenges I encountered while building the Tip Calculator App was ensuring proper validation for user inputs. Handling edge cases, such as preventing non-numeric characters, allowing only one decimal point, and displaying error messages when the bill or number of people is zero, required careful input sanitization. I overcame this by implementing a validation function that strips out invalid characters and limits decimal places, while also dynamically showing or hiding error messages based on user input.

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

I would appreciate feedback on a few specific areas of my project. First, I’d like to know if there’s a more efficient way to handle input validation, especially for preventing multiple decimal points and ensuring correct number formatting. Right now, I’m using a regex-based approach to sanitize inputs, but I wonder if there’s a more optimized or best-practice method for handling numeric inputs dynamically. Second, I’d love to get suggestions on improving accessibility, particularly in making error messages and result updates more screen-reader-friendly. Are there any recommended ARIA attributes or techniques I should implement to enhance usability for visually impaired users?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anthony Molina•290
    @LivexTwin
    Posted 4 months ago

    Looks great! Keep up the good work.

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