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

Responsive, Accessible Multi Step Form using Grid, Flexbox and JS.

accessibility, bem
Grego•1,430
@Grego14
A solution to the Multi-step form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Tried to use the maximum number of variables within the functions that I could. to avoid declaring them globally.

It's the first time I've written so much JavaScript code and I think it's all useful +500 lines, of course there are some things that could be done do to make it better.

i've been learning a little bit about A11y, such as the use of aria-hidden to hide icons and other elements.

In my next challenge I will try to use the mobile first approach for the first time! 😁

Edit: after sending the challenge I just realized that I put the background-color that wasn't the right one... (already updated)

Edit 2: solved some HTML report problems.

What challenges did you encounter, and how did you overcome them?

It was very difficult for me to make the mobile design because from a certain width everything began to overflow, what I did was to remove using media querys things like the width, paddings and sizes of some elements.

Bugs

  • I had a bug in the way I update the formStep as there were a few times where the animation and show classes they weren't eliminated, I solved it by iterating on all the form steps that aren't the new step and removing those classes.

  • had a bug that basically every time you went back to a formStep it added an eventListener from animationend and that's what caused it to glitches in the interface, as it ran the same code 1 time for each event... I solved it using the once property.

  • a bug in which I used animations for when you change formStep, before you change the actualFormStep to the nextStep the animation of the actualFormStep started to its initial state and you could see the element for a short time, I solved it using transitions instead of animations.

What specific areas of your project would you like help with?

I'd like to get help on the correct use of media queries and the way I did the design for mobile.

Also if someone could tell me if the way I implemented the Aria attributes I used is okay. 😁

I read in an article that you have to use default width and height in images in the HTML markup to avoid CLS, but I don't know if should use a picture element with different sources for things like icons, I would like help with that.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Grego's solution.

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.