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

Pomodoro App using Astro, Sass, Tailwind and Vanilla JS

accessibility, astro, sass/scss, tailwind-css
P
Kamran Kiani•2,780
@kaamiik
A solution to the Pomodoro 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 successfully implementing a fully functional Pomodoro app with a focus on accessibility and user experience. The integration of ARIA attributes to enhance accessibility and the use of local storage to persist user settings were significant achievements. If I were to do this project again, I would start by planning a more modular code structure to make the application easier to maintain and extend. Additionally, I would explore using a framework like react.

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

One of the main challenges I encountered was managing the layout and styling of the number inputs when adding the max attribute, which caused unexpected shrinking. I overcame this by setting the dialog's width to 100% and applying flex: 1; to the input's parent container, ensuring consistent sizing. Another challenge was ensuring the app's accessibility, which I addressed by incorporating ARIA attributes and seeking guidance from accessibility experts in the community.

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

I would like help with optimizing the performance of the app, particularly in terms of reducing any potential layout shifts or flickers when loading user settings. Additionally, guidance on implementing a more robust state management solution would be beneficial, as it could improve the scalability and maintainability of the application. Lastly, any advice on further enhancing the app's accessibility features would be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Arcloan•770
    @Arcloan
    Posted 4 months ago

    Really 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 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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub