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

Tip calculator app

react, vite, tailwind-css
AeroB•330
@AeroBW
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Darkstar•1,440
    @DarkstarXDD
    Posted 8 months ago

    Hey, your solution looks good, however i have few suggestions.

    • Instead of input type="text", you can use input type="number" for the bill, custom and people count. That way the user won't be able to enter any text entries at all. You can still do your validation in JS, but as a first layer of filtering i think it's far better to limit what the user can enter into the input fields.
    • The inputs needs labels. The elements bill, number of people should actually be label elements and their for attributes should point to the input element they are labelling. Currently you have them as p elements.
    • The icon images needs empty alt attributes. alt="". They are decorative images so no need any descriptive alt text but still the alt attribute needs to be their with an empty string. Otherwise some screen readers may read the file path of the icon as the alt text.
    • The error elements should have aria-live attributes. So when that element is populated with the error message it will be announced to screen reader users.
    • Ideally the tip buttons should be radio buttons (input type="radio") rather than normal buttons. For this design you will need to custom style the radio buttons if you went that way. There are few ways you can do that. How i have done it is visually hide the radio button and style the label to look like radio buttons and based on the checked and focus states of the radio button i styled the label.
    • I would put the logo image inside the main as well. Usually the logo image along with a navbar lives in the header landmark element but in this design i think it's fine to have it inside the main. Either way it should be inside an landmark element. Be it a header or the main. Currently it's not inside any.

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