Skip to content
  • Learning paths
  • Challenges
  • Solutions
  • Articles
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Vue 3 + Vite + Vueuse + Vue Draggable Solution

vite, vue, typescript
Jacob Longโ€ข70
@Jclong98
A solution to the Todo app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


How could I make this more accessible?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Travolgi ๐Ÿ•โ€ข31,320
    @denielden
    Posted about 3 years ago

    Hi Jacob, great work on this challenge! ๐Ÿ˜‰

    Here are a few tips for improve your code:

    • remove all unnecessary code, the less you write the better as well as being clearer: for example the div container of dark/light theme icon
    • instead of using px use relative units of measurement like rem -> read here
    • i can add task with with blanks, add a control... The trim() method can help you -> read here

    Overall you did well ๐Ÿ˜ Hope this help!

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