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

Intro component with input validation

accessibility, bem
Jason Greenwald•200
@jaycgreenwald
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • I split the JavaScript variables/error variables into it's own partial. It seemed useful to me. Is there a downside I'm overlooking?
  • It bugs me that when the 2px border is applied to the error fields, the form changes ever so slightly in size. I tried using outline instead of border, but I couldn't quite pull it off. I suspect I could have manipulated the padding via JavaScript but I was worried that was overkill. Suggestions?
  • How could I improve my JavaScript (syntax/formatting)? Can my code be simplified?
  • How can I improve accessibility?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello Jason, congrats on finishing the challenge, almost pixel perfect, great job!

    If you don't mind, I will try to do my best to answer your questions.

    1. Perfectly fine if you find your code more readable and organized, in popular frameworks for example, you will have all your code separated in a lot of files wich makes the code a lot more readable if it has a good organization.

    2. This is cause because you are adding those two extra pixels that push the other items down, you can get and easy work around with box-shadow instead of border, for this particular case try with: box-shadow: 0 0 0 2px rgb(255, 122, 122);

    3. Try selecting more things at once and loop at them, for example you could have selected all of your inputs and identify throw id's to use diferent validations on the same function but for diferent inputs, is a bit tricky to refactor, but using forEach() can help you a lot to refactor your code and make it more clear.

    4. I don't see that you are lacking that much on accessibility, you could for example use a section on the left div that is semantically related. Just don't forget to add alt tags to your images and structure well your document, so screen readers can have a better time.

    Hope my answers help you, if you have anymore questions don't hesitate to ask!

    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