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

Responsive user signup form using HTML, CSS and JavaScript.

accessibility, parcel, bem
Stephen Ikuomola•610
@stephenikuomola
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


Hello friends 👋🏽,

Great to announce that I have just completed yet another challenge, and I am happy with my solution. Client-side validation using JavaScript can be tricky sometimes, and it feels good I was able to come up with something for this one.

I learnt about the title attribute for form inputs, which I have not used before. This attribute helps provide some extra information about the element.

I will welcome any suggestions from the community on improving my solution.

Thank you 🙏🏽 .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 2 years ago

    I've just noticed you've used the 62.5% rem font size hack. It's worth reading this post about why I think that's a very bad idea

    That probably explains the strange font size and zoom behaviour I'm seeing on mobile too

    Marked as helpful
  • Grace•32,130
    @grace-snow
    Posted about 2 years ago

    Hi

    This looks pretty good! There are still some important points to learn

    1. Never add in extra content like this just for screenreader users <p class="sr-only">Fill out your information and access free trial.</p>
    2. Aria labels on form elements must be succinct and must begin with the name of the input. It should be "First name" not "Enter your first name". This is extremely important. For example some voice users would be unable to activate these inputs at the moment because "First name" would not activate the input as they expect. Overall you must not try so hard when attempting accessible code - keep it simple and don't over complicate otherwise you end up making it accidentally inaccessible!
    3. Also note that aria-label does not consistently translate. So it may be better to use an Sr-only label element on the inputs instead.
    4. The title attribute is not good to use on inputs. You are giving additional information there that would be inaccessible to some users. If its important info it has to be present in an element on the page and linked to its input with aria-desciribedby
    5. To programmatically link error messages to their inputs, give the error message container a unique ID and use aria-desciribedby on the input pointing to that ID
    6. You must NEVER have click listeners on non-interactive elements. That password reveal toggle must be a labelled button and must communicate state with aria- pressed. The position of that button seems incorrect too - I'll add a screenshot to discord so you can see what I'm seeing
    7. This isn't a very accessible design, but you can improve it slightly by adding a unique ID to the terms and aria-desciribedby on the submit Button pointing to that ID. This will make sure the terms acceptance is read out to AT users along with the submit Button
    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub