Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Responsive Time tracking App using flex+JS

_nehal💎•6,710
@NehalSahu8055
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👋Hello, Frontend Mentor coding community.

👨🏼‍💻This is my solution for the Time tracking App.

🎨 I added some custom features:

  • 🪄 Hover Effects
  • 🫧 CSS Animations
  • 👆 Clickable 3 dots

I'll be happy to hear any feedback and advice!🤗

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,360
    @0xabdulkhaliq
    Posted about 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    HEADINGS ⚠️:

    • This solution consists incorrect usage of <h1> so it can cause severe accessibility errors due to incorrect usage of level-one headings <h1>

    • Every site must want only one h1 element identifying and describing the main content of the page. But using that for a person name is not appreciated

    • An h1 heading provides an important navigation point for users of assistive technologies, allowing them to easily find the main content of the page.

    • In this solution there's <h1> element which is this <h1>Jeremy Robson</h1>, you can preferably use <h2> instead of <h1>. Remember <h1> provides an important navigation point for users of assistive technologies so we want to use it wisely

    • So we want to add a level-one heading to improve accessibility by reading aloud the heading by screen readers, you can achieve this by adding a sr-only class to hide it from visual users (it will be useful for visually impaired users)

    • Example: <h1 class="sr-only">Time tracking dashboard</h1>

    • If you have any questions or need further clarification, you can always check out my submission for another challenge where i used this technique and feel free to reach out to me.

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • 🦊[Shadow]🦊•420
    @Shadow-IO-oI
    Posted about 2 years ago

    Hey there! 👋

    Congrats on successfully completing the challenge! 🎉

    I wanted to share some suggestions with you regarding your code that I think you'll find helpful. Specifically, with regards to the CSS🖼️:

    It looks like there is a problem with the hover effect on the items when the focus is on the rear decoration image and not on the "main-box". One solution to this issue is to add an additional class for each item, for example, "item-hover". Then, you can rewrite the ".main-box:hover" line in CSS to target the ".item-hover:hover .main-box" selector, which will solve the hover effect problem:

    .item-hover:hover .main-box {
      top: -10px;
      background-color: var(--dbl);
      cursor: pointer;
    }
    

    With this updated code, the hover effect issue should be resolved.

    I trust that you'll find this recommendation useful, and once again, congratulations on your fantastic solution! Keep up the great work and enjoy coding! 🦊👍

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

Oops! 😬

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

Log in with GitHub