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

vanilla multi page form

Aryan Kumar•390
@aryanda1
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Maciej Narejko•180
    @MaciejNarejko
    Posted about 2 years ago

    Hello there 👋

    Here's the feedback:

    • When the user goes to at least the second step and then goes back to the first step, the "Go Back" button should be not available in the first step. Add a condition in the goBack() function to handle the case when currentPageNumber is 1.

    • After entering all fields incorrectly on the first page of the form, and then correctly filling in some of them, the error message for those correct fields does not disappear.

    • The background and foreground colors do not provide sufficient contrast ratio, which can strain the user's eyes. Consider adjusting the color scheme to ensure better readability and accessibility.

    • The document lacks a meta description tag <meta name="description">.

    • Remove unused code, such as the addOnLabels array: const addOnLabels = ["Online Service", "Larger Storage", "Customizable Profile"];

    • Replace occurrences of var with let or const for consistency. For example: let label = checkbox.parentNode;

    • Consider extracting reusable code into helper functions to improve modularity and readability.

    I hope I provided at least some useful feedback. Happy coding 🙂

    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

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