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

Intro component with sign up form with ReactJS & styled-components

Rizky P. Mahendra•390
@rizky-pm
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 use 1366 x 768 screen size, but the design size is 1440 x 800. I use figma to measure the size of every component but the final result is never 100% same, any tips for measurement will be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. Layout in desktop looks great, the responsiveness could be better, since right now, there is a point where horizontal scrollbar appears. Also, the mobile layout is too soon, at point 1010px I think, you already set the mobile layout, which is too big.

    Well, the design is made for that size right, that means if you use 1366x768 like I do, we won't get the exact size. What you could is that, adjust the size of your figma's canvas? I don't use figma, I only used adobe xd, change the size to 1440 so that the layout will fit perfectly, at there, you could get the exact result.

    Some other suggestions would be:

    • Avoid using height: 100vh on a large container. This makes the element's height, only limited to the remaining screen/viewport's height. Instead, use min-height: 100vh, this takes full height and will expand if it needs to.
    • You don't really need a header on this one. This one whole component should be inside the main element. So after your root selector, you could have used main element to wrap all content.
    • On each input, it would be better to only show the error-message, when the user "submits" the form, not for every focus on the element. Try clicking on the input and click on another, the error-already show even if the user didn't make any changes.
    • For each input, if the input is wrong, you should add aria-invalid="true" on the input element. This informs a user that their input is wrong.
    • Also, the error-message element should have an id attribute. This will be referenced by the aria-describedBy which you will use on the input element.
    if ( input is wrong) 
      input.setAttribute("aria-invalid", "true");
      input.setAttribute("aria-describedBy", { id of the error-message });
    else 
      input.removeAttribute("aria-invalid");
      input.removeAttribute("aria-describedBy");
    

    This creates a bridge to which users will not be confused, since they will be informed, if they have entered a wrong input and what type of error did they make.

    • The error-message icon should have alt="' and aria-hidden="true" on it. Always remember to include the alt attribute.
    • As an addition to making this more accessible, you could add an aria-live element, to which will announce if the form submitted has any error or if the form is a success.

    Aside from those, check the responsive state about the horizontal scrollbar. Great work again on this one.

    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