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

TIP CALCLATOR APP

accessibility
1deadjoe•370
@1deadjoe
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 proud I was finally able to grasp JavaScript syntaxes that were giving me a rpoblem earlier. Such as the correct use of forEach(). I was able to come up withe the design in a much shorter period of time, and without having to go research in order to figure out how to style different components.

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

My challenge was handling the user inputs, but after going through a few Javascript documentations, I got the hang of it.

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

I would highly appreciate assistance it finding better ways to write my JS code, checking how semantic my HTML is. Anyone whose approach was different to mine could give feedback so I could check theirs out.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Martin Liesche•590
    @marliedev
    Posted 7 months ago

    Hey deadjoe! Overall your solutions looks fine, but could be improved in some ways. Maybe my feedback helps:

    Calculation

    • is not correct! The total amount should be let totalTip = billValue / peopleValue + tipValue;

    Validation:

    • you could have also added validations / feedback for the bill amount and custom tip value. When i leave those blank the result is NaN

    Semantic Markup:

    • dont put <header> inside the main element. The <header> should only be used above the main (for e. g. a navbar with logo) or inside an <article> element
    • you could have used a form and radio-group for the inputs. This way the form-handling and also accessibility could be improved.

    JavaScript:

    • More comments! Thats crucial!
    • Naming could be improved and more clearly/readable. "handleClick()" is not clear enough for the tip-buttons. Better: handleTipButtonClick()
    • You could have added the base values directly inside the <input value="">

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