Skip to content

Latest commit

 

History

History
69 lines (41 loc) · 2.95 KB

README.md

File metadata and controls

69 lines (41 loc) · 2.95 KB
Raw

Form validation challenge

Practice validating user input in the browser.

Setup

Make sure you have Git and Node (v18) installed.

  1. Use this template, clone your copy, cd into it
  2. Run npm install to install all the dependencies
  3. Open challenge/index.html in your browser

Checking your work

Each challenge has associated unit tests. You can either run all the tests with npm test, or each individual challenge's tests with npm run test:1, npm run test:2 etc.

Make sure you read test failures carefully—the output can be noisy but the error message should provide useful information to help you.

Challenge 1: Required fields

The form in challenge/index.html can be submitted without filling out any of the fields. Without adding any JS make sure these fields are present:

  1. The name input
  2. The email input
  3. The message textarea

Make sure to mark these fields as required so the user knows they must fill them in.

Challenge 2: Different types of fields

Currently all the fields accept anything as input. Without adding any JS make sure each of these fields is restricted to its type:

  1. The email input should be a valid email
  2. The website input should be a valid URL

Challenge 3: Limit length

Some users are sending excessively long messages. Without adding any JS makes sure the message textarea only accepts up to 140 characters.

Make sure to tell the user about the limit so they aren't surprised when they try to submit.

Challenge 4: Prevent uppercase

Users keep shouting at us, and it makes us feel bad. Without adding any JS make sure the subject input can only contain lowercase letters, numbers, and spaces.

Challenge 5: Validity state for assistive tech

The validity of each field is not consistently exposed to assistive technologies like screen readers. Write some JS in challenge/index.js that uses the aria-invalid attribute to help:

  1. Mark all fields as valid at first
  2. When a field fails validation mark it as invalid
  3. When a field is edited mark it valid again

Challenge 6: Put validation messages in the DOM

The validation messages shown by the browser cannot by styled, and are not consistently exposed to assistive technologies. Write some JS in challenge/index.js to add these messages to the DOM instead:

  1. Create a new element to hold each message
  2. Associate this element with its field
  3. When a field fails validation add the browser's default message to the element
  4. When a field is edited remove the message

Challenge 7: Disable built-in form behaviour

It's a bit confusing for users now as the validation messages show up in two places: the default popup bubble and your new DOM element. Write some JS in challenge/index.js to disable this built-in behaviour:

  1. Stop the <form> element validating fields
  2. Manually check whether all the fields are valid
  3. If not prevent the form submission from taking place