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

Responsive Multi Step Form

tailwind-css, typescript, vite, vue, accessibility
Mahmoud Tarek•670
@mahmoudAcm
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


First-Time Vue Experience: Responsive Multi-Step Form Challenge

I recently took on a challenge to create a responsive multi-step form using Vue.js. Previously, I had tackled the same project using React. You can check out my React.js solution here.

I'm eager to receive feedback from the Vue.js community to ensure I made the right decisions for this specific Vue project, considering it's my first time using Vue. If there's a better way I could have built it or any improvements you suggest, please don't hesitate to share your insights. Your feedback will be greatly appreciated!

Happy coding! 🚀

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Korney Chervonenko•1,080
    @KorneyChervonenko
    Posted 5 months ago

    I think you shouldn’t use "display: none" to hide titles in menu in mobile layout. It’s worth to read: https://stackoverflow.com/questions/62107074/how-to-hide-a-text-and-make-it-accessible-by-screen-reader/62109988

    Marked as helpful
  • Felipe Stefani•330
    @felipestefani
    Posted almost 2 years ago

    Hey, Mahmoud!!

    Your designs are always great! I've been following you since a while and it's very good to see how your projects are.

    In this one, the only observation to do is in your logic. When selecting the additional, whether selected or not, the total includes all of them. I didn't check the code at all, but thinking about it it's a simple thing to correct.

    Beside that, as I've already said, I love to see the results you show to us ☺️

  • Eric Teye•40
    @ericaimhigh1
    Posted almost 2 years ago

    I'd say that's a great 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, 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

Oops! 😬

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

Log in with GitHub