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

Time tracking dashboard using HTML, CSS, JavaScript

accessibility, fetch
P
Aydan•680
@AydanKara
A solution to the Time tracking dashboard 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?

✅ Proud of:

  • Successfully integrating JSON data to dynamically update the UI.
  • Implementing responsive design that adjusts well for different screen sizes.
  • Smooth hover effects and interactive elements for better user experience.
  • A clean and structured JavaScript logic that makes adding future features easier.

🔄 What I'd do differently next time:

  • Improve accessibility by adding ARIA attributes and ensuring keyboard navigation works smoothly.
  • Optimize performance by lazy-loading images and reducing redundant DOM queries.
  • Ensuring Smooth Transitions Between Timeframes
  • Switching between Daily, Weekly, and Monthly felt abrupt.
  • Use a framework (React or Angular) to make state management easier and cleaner.
What challenges did you encounter, and how did you overcome them?

Challenge 1: Dynamically Updating Data from JSON

  • Initially, the hours and previous stats were hardcoded in HTML.
  • Solution: Used JavaScript to fetch the JSON and update the UI dynamically based on selected timeframes.

Challenge 2: Mobile Responsiveness

  • The original layout didn’t fit well on smaller screens.
  • Solution: Used CSS Grid adjustments and media queries to make it fully responsive.
What specific areas of your project would you like help with?

🤔 Areas for Feedback & Improvement:

  • Code Optimization: Are there better ways to structure the JavaScript for cleaner, more efficient updates?
  • Performance: Are there ways to reduce the number of DOM queries and improve efficiency?
  • Accessibility: How can I make the UI more accessible, especially for keyboard and screen reader users?
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • AnshShrivastava70•60
    @AnshShrivastava70
    Posted 4 months ago

    This looks amazing! The design is absolutely perfect, and I love how well-structured your GitHub README is. Really inspiring 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
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, SASS, 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