WRWEB ENGINEERING
REFORGING10 · 3/7
ALL LESSONS→WEEK 10→WEDNESDAY

CONSTRAIN · HTML TO THE FRONTIER

Native validation

Forms are state machines30–60 MINUTESCORE + PRACTICAL
01

GROUND

Problem

What becomes confusing, fragile, or impossible without understanding native validation? This lesson answers that through explanation, a worked example, two runnable exercises, and a reference solution. No teacher-supplied worksheet is required.

HTML evolved from linked documents into a semantic application platform with forms, native validation, disclosure, dialogs, media, and accessibility mappings.
02

LEARN

Concept explanation

Native validation belongs to “Forms are state machines”. native validation is learned by comparing readable, constrained, and deliberately clever implementations against same evidence.

For native validation, trace concrete input, state transition, output, and failure through a parser-to-DOM-to-accessibility-tree contract with native behavior before JavaScript.

Markup enters a parser, becomes a DOM, maps into accessibility semantics, and exposes native controls with built-in state and behavior. Apply that model to supplied normal, boundary, and failure cases; each case below names its input and expected evidence.

Observable

Evidence produced by the native validation experiment: output, state, trace, bytes, timing, or diagnostics.

Invariant

Condition that must remain true while inputs or implementation of native validation change.

Boundary

Point where native validation crosses ownership, representation, time, process, network, or trust.

Example bank

Compare normal, boundary, failure, and cross-layer cases. Predict each observation before revealing the explanation.

Baseline · one variable

SETUPSolve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls.

OBSERVEAll versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost.

WHY IT MATTERSThis isolates the normal contract of native validation; preserve its raw evidence as the control for every later comparison.

Boundary · same contract, harder input

SETUPRun all three implementations against: Submit empty, invalid, then valid data and inspect FormData.

OBSERVERecord what remains invariant and the first representation, owner, size, or timing value that changes in Chromium Elements · Accessibility · Network.

WHY IT MATTERSA boundary example is useful only when one named dimension changes and everything else stays comparable.

Failure · evidence before repair

SETUPForce every implementation through: Disable or unname one control and explain why it vanishes from payload.

OBSERVECapture the first divergence from the baseline, including exact input, diagnostic, state, and recovery result. Expected recovery: All versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost.

WHY IT MATTERSThe diagnostic is part of the interface. Repair the proven cause, not the most visible symptom.

Cross-layer · follow ownership

SETUPTrace native validation one layer below its usual abstraction through a parser-to-DOM-to-accessibility-tree contract with native behavior before JavaScript.

OBSERVEUse Elements and Accessibility panels; compare source markup, DOM properties, focus order, accessible names, and submitted form data.

WHY IT MATTERSThe lower layer is earned when it explains evidence the current layer cannot. Otherwise keep native validation at the simpler boundary.

03

SEE

Worked example

Start from supplied index.html. Focus: Solve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls.

  1. Run: Open index.html directly, then inspect DOM and Accessibility trees.
  2. Save baseline evidence. Use Elements and Accessibility panels; compare source markup, DOM properties, focus order, accessible names, and submitted form data.
  3. Boundary case: Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData.
  4. Failure case: Force every implementation through: Disable or unname one control and explain why it vanishes from payload.
RESULT
All versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost. Starter-level baseline: Page has one main landmark, one level-one heading, a correctly named input, native required validation, and a submit action.
04

START HERE

Starter material

PREREQUISITESA modern browser and plain-text editor. No package install or server required for baseline lessons.

ONE-TIME SETUPCreate an empty folder, save starter as index.html, then use browser File → Open File to open it.

Create index.html, paste this exact content, then run the command below.

<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>native validation</title>
<main>
  <h1>native validation</h1>
  <form><label>Observation <input name="observation" required></label>
    <button>Submit</button></form>
  <output aria-live="polite">Ready</output>
</main>
RUNOpen index.html directly, then inspect DOM and Accessibility trees.

STOP / CLEANUPClose the browser tab when finished; the file remains portable.

05

DO WITH GUIDANCE

Guided exercise

Solve under constraint: native validation

  1. Normal case: Solve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls.
  2. Write predicted evidence from this named case before running starter.
  3. Keep readable baseline, then remove one convenience without hiding behavior.
  4. Run exact normal case. Save commands, inputs, outputs, and diagnostics in notebook.
  5. Explain changed evidence using lesson mental model in no more than five sentences.
Concrete guided solution
  1. Copy the supplied index.html unchanged and run: Open index.html directly, then inspect DOM and Accessibility trees.
  2. Write this prediction before inspecting output: All versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost.
  3. Perform only the named normal case: Solve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls.
  4. Save the raw output, then annotate input → transition → evidence. Use Chromium Elements · Accessibility · Network to confirm the transition rather than inferring it.
  5. Compare prediction with evidence; if they differ, keep both and write the rule that explains the difference. Reference baseline: Page has one main landmark, one level-one heading, a correctly named input, native required validation, and a submit action.
06

DO ALONE

Independent exercise

Compare three versions: native validation

  1. Create second case from blank file: Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData.
  2. Then create controlled failure: Force every implementation through: Disable or unname one control and explain why it vanishes from payload.
  3. Use Chromium Elements · Accessibility · Network to prove behavior, then repair controlled failure.
  4. Compare result against supplied acceptance checks and reference approach before marking complete.
Concrete independent solution
  1. Duplicate the starter into a clean comparison case; change only this boundary: Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData.
  2. Save its evidence beside the baseline and identify the first changed value. Use Elements and Accessibility panels; compare source markup, DOM properties, focus order, accessible names, and submitted form data.
  3. Create the exact controlled failure: Force every implementation through: Disable or unname one control and explain why it vanishes from payload.
  4. Version A: use clearest native primitives and name every intermediate state for native validation.
  5. Version B: remove one convenience while preserving same input/output contract.
  6. Version C: compress only after A and B pass baseline: Build labeled required email, radio group, textarea, submit, and reset controls.
  7. Run shared boundary and failure fixtures against all versions: Submit empty, invalid, then valid data and inspect FormData. / Disable or unname one control and explain why it vanishes from payload.
  8. Keep A unless another version has measured benefit; expected invariant: Native validation blocks invalid state; valid payload contains successful named controls only.
  9. Rerun baseline, boundary, and repaired failure together. Accept only if all reproduce: All versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost.
07

COMPARE

Expected result

  • All versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost.
  • Page has one main landmark, one level-one heading, a correctly named input, native required validation, and a submit action.
  • Controlled native validation failure produces captured evidence; repair restores stated invariant without hiding error.
08

PROVE

Acceptance checks

Lesson is complete only when every check is true. Each check is stored locally and travels with your JSON backup.

0/5 complete · saved on this device

09

UNSTICK

Hints

Reveal hints
  1. Start with supplied normal case exactly as written: Solve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls.
  2. For boundary case, change only named dimension: Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData.
  3. If result is confusing, diff raw inputs and evidence before editing implementation.
  4. If tool shows nothing useful, move observation one boundary lower: representation, runtime, OS, or network.
10

VERIFY

Solution

Attempt both exercises before opening reference approach.

Reveal reference solution
  1. Run unmodified starter and preserve baseline evidence: Page has one main landmark, one level-one heading, a correctly named input, native required validation, and a submit action.
  2. Version A: use clearest native primitives and name every intermediate state for native validation.
  3. Version B: remove one convenience while preserving same input/output contract.
  4. Version C: compress only after A and B pass baseline: Build labeled required email, radio group, textarea, submit, and reset controls.
  5. Run shared boundary and failure fixtures against all versions: Submit empty, invalid, then valid data and inspect FormData. / Disable or unname one control and explain why it vanishes from payload.
  6. Keep A unless another version has measured benefit; expected invariant: Native validation blocks invalid state; valid payload contains successful named controls only.
11

PREDICT · INSPECT · BREAK · DEBUG · MEASURE

Interrogate reality

Prediction: write expected output, state transition, ordering, and failure evidence before running either exercise.

Inspection: Use Elements and Accessibility trees; compare attributes, properties, focus order, form data, and no-JavaScript behavior.

Measurement: Measure transferred bytes, parse cost, interaction readiness, keyboard steps, and failure behavior without scripts.

INSPECT

Capture raw evidence before explaining.

BREAK

Change one assumption and force controlled failure.

DEBUG

Find cause with Chromium Elements · Accessibility · Network before editing fix.

TOOL DRILL · keyboard only · record one retrievable command or shortcut
12

MASTERY + FRONTIER + BOUNDARY

Own the knowledge

TEACH

Explain native validation at beginner, intermediate, and senior depth.

REBUILD

Recreate smallest useful example from blank file without notes or AI.

RETRIEVE

Schedule recall for day 1, 7, 30, and 90.

Creative frontier lab

Try first without opening the solutions. The constraints invite invention; the reference gives one concrete direction, never the only valid answer.

Constraint inversion

Re-solve native validation by removing the most convenient abstraction. ship the interaction with native elements and zero custom JavaScript.

CONSTRAINTKeep the same inputs, observable result, and failure evidence; change the means, not the contract.

ORIGINAL IDEATurn subtraction into a design tool: the missing abstraction should reveal which responsibility it used to hide.

Reveal frontier solution
  1. Freeze the contract as three fixtures: Solve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls. / Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData. / Force every implementation through: Disable or unname one control and explain why it vanishes from payload.
  2. List every convenience used by the starter; remove the highest-level one while preserving Open index.html directly, then inspect DOM and Accessibility trees..
  3. Implement the smallest replacement using ship the interaction with native elements and zero custom JavaScript.
  4. Run all fixtures and compare raw evidence. Keep the simpler version unless the removed abstraction has a demonstrated benefit.
Representation x-ray

Build an explanation artifact for native validation: compare source, parsed DOM, focus order, form payload, and accessibility tree.

CONSTRAINTA peer must be able to locate the first divergence without reading implementation code.

ORIGINAL IDEATreat the explanation itself as a product: make invisible transitions visible, replayable, and diffable.

Reveal frontier solution
  1. Create one row or timestamped event for each transition in: Solve native validation three ways using identical fixture: Build labeled required email, radio group, textarea, submit, and reset controls.
  2. For every row record input, representation, owner, operation, output, and tool evidence from Chromium Elements · Accessibility · Network.
  3. Replay Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData.; highlight only changed rows.
  4. Replay Force every implementation through: Disable or unname one control and explain why it vanishes from payload.; stop at the first divergent row and attach its recovery action.
Adversarial remix

Combine the boundary and failure into a new user-visible scenario for native validation. make one document usable by keyboard, screen reader, print, and direct URL fragments.

CONSTRAINTDo not merely add more input. Invent a recovery interaction, alternate representation, or self-checking behavior.

ORIGINAL IDEAMake the system teach its own limits: the artifact should expose the invariant and offer a safe next action when it breaks.

Reveal frontier solution
  1. Combine these two pressures without changing them: Run all three implementations against: Submit empty, invalid, then valid data and inspect FormData. AND Force every implementation through: Disable or unname one control and explain why it vanishes from payload.
  2. Name the invariant that must survive and the user-visible evidence when it cannot: All versions preserve Native validation blocks invalid state; valid payload contains successful named controls only.; comparison records code size, predictability, and debugging cost.
  3. Implement this original direction: make one document usable by keyboard, screen reader, print, and direct URL fragments.
  4. Demonstrate baseline, combined failure, recovery, then baseline again; save the sequence as a regression fixture.

Capability frontier

Push native validation until another layer becomes justified. Record one robust technique, one contextual trade-off, and one labeled hack or historical curiosity.

CORE · PRACTICAL · CONTEXTUAL · HACK · FRAGILE · HISTORICAL · GOLF

Boundary

HTML coordinates navigation and submission well, but complex local computation and synchronization quickly become awkward.

If this vanished tomorrow…

Return to meaningful text, links, forms, HTTP requests, and browser defaults.

Why next layer is earned

CSS is earned when correct semantics need deliberate layout, hierarchy, responsive behavior, and visual state.