DiscoveryVIP / HTML & CSS AcademyHelp

30. HTML form validation

Module 6 · About 20 minutes · Lesson 29; review earlier concepts as needed

Open Interactive Lesson

Discover

What changes when you use html form validation, and how can you prove it?

Predict

Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.

Understand

Native constraint validation uses attributes such as required, minlength, min and type. It helps users catch mistakes but cannot replace server-side validation. Error presentation varies by browser. Do not disable validation without providing an equally useful alternative. The sandbox can inspect valid and invalid states without making an external request.

Important source lines

index.html:1 <form><label>Display name <input name="display" required minlength="3" maxlength="30"></label><button>Check sample input</button></form>
A group of named controls for a submitted task. Attribute guidance: action/method for real delivery; local preview intercepts submission.
styles.css:1 input:invalid { border:2px solid #a52a24; } input:focus-visible { outline:3px solid #1e63a3; }
This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.

The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.

Example 1: HTML form validation

The input declares a minimum length and remains required; invalid appearance is supplemented by native validation.

index.html

<form><label>Display name <input name="display" required minlength="3" maxlength="30"></label><button>Check sample input</button></form>

styles.css

input:invalid { border:2px solid #a52a24; } input:focus-visible { outline:3px solid #1e63a3; }

script.js

Expected: The input declares a minimum length and remains required; invalid appearance is supplemented by native validation.

Edit and Render This Example
Example 2: Element: form

A group of named controls for a submitted task.

index.html

<form><label>Name <input name="name" required></label><button>Preview locally</button></form><p>Delivery needs a configured backend.</p>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A group of named controls for a submitted task. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 3: Element: label

A visible programmatic name for a control.

index.html

<label for="email">Email</label><input id="email" name="email" type="email">

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A visible programmatic name for a control. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 4: Element: input

A native control whose type selects a data/interaction contract.

index.html

<label>Quantity <input type="number" name="quantity" min="1" max="6" value="1"></label>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A native control whose type selects a data/interaction contract. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example
Example 5: Element: button

A native action control with keyboard behavior.

index.html

<form><label>Name <input name="name" required></label><button type="submit">Preview</button><button type="reset">Reset fields</button></form>

styles.css

body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }

script.js

Expected: A native action control with keyboard behavior. Review its real DOM and native behavior; structural/media-only examples are labeled.

Edit and Render This Example

Build and test

The input declares a minimum length and remains required; invalid appearance is supplemented by native validation. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.

Starter index.html

<form><label>Display name <input name="display" required minlength="1" maxlength="30"></label><button>Check sample input</button></form>

Starter styles.css

input:invalid { border:2px solid #a52a24; } input:focus-visible { outline:3px solid #1e63a3; }

Objective contract

[
  {
    "type": "attr",
    "selector": "input",
    "property": "minlength",
    "value": "3",
    "label": "input has minlength=3"
  }
]
Hint 1

Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.

Hint 2

The relevant source uses minlength="3". The exercise instead uses minlength="1". Identify its effect before changing it.

Hint 3

Restore the intended minlength="3" operation or implement an equivalent structure/style. Run the actual checks and explain why it works.

Complete reference solution

index.html

<form><label>Display name <input name="display" required minlength="3" maxlength="30"></label><button>Check sample input</button></form>

styles.css

input:invalid { border:2px solid #a52a24; } input:focus-visible { outline:3px solid #1e63a3; }

Explain, reflect and extend

Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.

Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.

Troubleshooting and professional practice

If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. The input declares a minimum length and remains required; invalid appearance is supplemented by native validation.

Knowledge check

Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.

Optional AI prompts

  1. Explain this lesson’s source line by line using the actual objective above.
  2. Help implement one small extension and define normal, boundary and failure tests.
  3. Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.

Continue to Lesson 31: Your first CSS styles

Detailed learning and editor help · Standards reference