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

Tip-Calculator-App

T23harms•540
@T23harms
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Erick Rodrigues•660
    @SortJakke
    Posted 4 months ago

    Design and functionality:

    • The calculator is currently accepting negative values, which could compromise its functionality in scenarios where only positive numbers are needed.
    • The error message is misaligned, and the input does not change its border when displaying an error, which affects visual perception and usability.

    Suggestions for the code:

    • I recommend using position: absolute on the error span and aligning it according to the specified design to ensure visual consistency.
    • Input images can be added via background-image in the CSS, simplifying the HTML and making design adjustments easier.
    • Using a label associated with the input is more semantically correct and provides accessibility benefits, such as improved interaction for users relying on assistive technologies.
    • To prevent negative values in numeric inputs, you can add the min="0" attribute directly in the HTML. However, the more robust approach would be to implement validation in JavaScript, providing greater control over the data entered.
    • Using a <form> to wrap the calculator elements would make the code more organized and semantic while also facilitating JavaScript integration for event handling and validations.

    Final considerations: Despite these adjustments, the solution presented is visually aligned with the proposed design and offers a functional experience that would work well for an average user. Congratulations on the work!

    Marked as helpful

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

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