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

Time Tracking Dashboard (HTML, CSS, JS)

FesoQue•380
@FesoQue
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Not perfect but constructive feedback will be appreciated

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. Layout looks really good and it responds well, the mobile layout is great as well.

    Some suggestions would be:

    • The img for the person should have used their name as the value like alt="Jeremy Robson", always make the alt meaningful if the image adds content.
    • On this one, I wouldn't really use the h1 for the name of the person, I would make the h1 a screen-reader only text to give overview of the whole webpage.
    • Also, why place:
    <h1> Jeremy Robson</h1>
    <p>Report for </p>
    

    This makes the html in wrong order, it should be swapped, then just use `flex-direction: column-reverse" on the flex parent.

    • Those numbers like 5hrs 1hrs they shouldn't have been the heading, since they don't really give any extra information, the work play those are the ones that should be the heading, because if a user navigated on them, they would know that this section tells them about the work, tells them about the play.
    • The alt for the elipsis images should have been left empty like alt="", since those are just decorations.
    • Those button should not have role="button" since those are already button. Also an addition, since that part is a selection, using input type="radio" on those would be great, since you can only choose 1, and radio buttons are intended for those, using it would add extra accessibility on your website because unlike button there is no extra information if a user toggles it, unless you use other aria's or alert.
    • Those selections as well should have visual indicator, if you remove the outline make sure to add something to the :focus-visible state of the selector.

    Aside from those, great work.

    Marked as helpful
  • P
    Karthik suryadevara•865
    @karthik2265
    Posted almost 4 years ago

    Looks nice There are 2 issues I found

    1. looks like there is border at the bottom of cards to handle this try putting margin to 0
    2. in javascript you forget to update text along with number of hours i.e for daily it should be yesterday and for monthly it should be last month
    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, 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

Oops! 😬

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

Log in with GitHub