Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Multistep Responsive form built with html, css & vanilla js

Kedar Agate•70
@kedaragate
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Is it good?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bruce B•485
    @bbsmoothdev
    Posted over 1 year ago
    .btn {
      outline: none;
    }
    

    You should never remove the keyboard focus indicator. People who can only use a keyboard to access your page rely on that. Removing the focus indicator is basically the same as using a mouse but not being able to see the mouse pointer.

    If you don't want mouse users to see the focus indicator then you can style :focus-visible, which will only show up when someone is using a keyboard. In fact, that's what all the browsers use by default now. But when you set outline: none then you remove that completely.

    You've also removed it for the inputs. That's not quite as bad because you will still see the blinking text cursor. But really, you should have a focus indicator for the text inputs as well. Yes, even if you use :focus-visible the outline will still show up for mouse users. Just make it look cool and that will be OK.

    But if you don't want to create your own focus outline styles then just remove outline: none and rely on the browser defaults. It won't be quite as good as rolling your own, but at least it will be something.

    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