Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Time Tracking Vue App

Fraser Watt•1,790
@fraserwat
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any tweaks much appreciated!

For some reason the preview comes up with a stretched profile image, but this isn't replicated at any page width as far as I can see 🤷‍♂️

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Krista Calleja•300
    @KristaCalleja
    Posted over 3 years ago

    Hi @fraserwat, I have been going through your projects and I love your work. I'm taking note of your approaches to learn more. I am very newbie in comparison to you and of course, I feel very "little" to advise you, however the profile-card img is also showing stretched on my Firefox browser. I tried adding height: auto to it and it seemed to address it (though it affects the other cards too). Looking forward to seeing more of your work.

    Marked as helpful
  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, great work on this one. Layout in desktop looks really great, it is responsive and the mobile state looks great as well.

    Yeah, I tried to zoom out as well and can't reproduce on the screenshot, does taking another screenshot cannot take the bug away?

    Some suggestions would be:

    • Person's img should be using the person's name as the alt like alt="Jeremy Robson". The person's image is meaningful since the component is highlighting the person's profile.
    • You don't really need to use nav in here since there are no navigational links that are currently present. Instead, since you are using a set of radio buttons, use fieldset instead of nav, add as well a screen-reader only legend element, this legend's text-content will describe what is the set of radio buttons are for.
    • Your set of radio buttons have no visual indicator right now, so tabbing on it doesn't show where the users is currently at. On this, personally I would use a fieldset:focus-within and add an outline to the fieldset but I might trim down the fieldset's width so that it won't be large, I might first wrapped the fieldset in a div so that I could control its size properly.
    • Each input should have the same size as their label and they should placed right underneath the label, just make sure the label is above each input. Because by using width: 1px this makes the input have like no appearance when using screen-reader. Typically when using screen-reader there is another outline that covers a control element, this is an indicator for other users as well since not only not-sighted users uses screen-readers and providing indicator is always necessary. So each input is placed where their label is placed.

    Aside from those, site looks great and awesome again on this one.

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

Oops! 😬

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

Log in with GitHub