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

Accessible Tip Calcutor App (SASS + SEO)

accessibility, lighthouse, sass/scss, animation
Alberto José•630
@alberto-rj
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?

The main feature of this project is the ability to automatically calculate the tip and total bill based on user inputs. The calculation logic is implemented in JavaScript, ensuring precise results and real-time updates as users interact with the input fields.

Next time, I plan to build this challenge completely from scratch using React.js.

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

♿️ 1. Accessible Validation

  • Problem: The app must remain accessible during user input validation.
  • Solution:
    • ✅ Implementation of accessible validations.
    • ✅ Clear and informative error messages.
    • ✅ Tested on different devices to ensure an inclusive experience.

💡 2. Interactive Visual Feedback

  • Problem: Need to implement hover and focus states for all interactive elements on the page.
  • Solution:
    • ✅ Use of CSS pseudo-classes :hover and :focus-visible.
    • ✅ Ensured consistent visual feedback on buttons and fields.
    • ✅ Improved usability and accessibility of the app.

💻📱 3. Responsive Layout

  • Problem: The layout must be optimized for different screen sizes.
  • Solution:
    • ✅ Implemented media queries to adjust the layout.
    • ✅ Used relative units (such as %, and rem) to ensure scalability.
    • ✅ Applied Flexbox and CSS Grid to create a flexible and adaptable layout.
    • ✅ Tested on various devices to ensure proper viewing.

💰 4. Precise Tip Calculation

  • Problem: The app must accurately calculate the tip and total cost per person.
  • Solution:
    • ✅ Implemented precise calculation functions in JavaScript.
    • ✅ Ensured that results are displayed clearly and understandably.
What specific areas of your project would you like help with?

I would like to receive feedback on the:

  • Accessibility approach I have adopted.
  • README.md as seen by recruiters or employers.
  • Or any other feedback you may have. 😊👍
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 Alberto José'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 1st-party linked stylesheets, and styles within <style> tags.

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.