HTML Form Usability
Project workbook · Path 92

Build and review a small semantic HTML form with labels, useful validation and a clear local-only submission state.

The case

A fictional workshop interest form asks for a name, an optional email and a preferred session. Email is optional because the practice does not send confirmations. The local demonstration must explain that no data is transmitted or stored.

FieldRequiredRule
Nameyesnonblank
Emailnoemail format if supplied
Sessionyeschoose morning or afternoon
STAGE 1

Choose fields that serve the task

Ask only for information needed for the stated task. Use appropriate native controls and associate labels explicitly. A placeholder can illustrate format but disappears during entry, so it cannot carry the only instruction. This local example avoids collecting real personal information.

Your task

Create the three-field semantic form.

Required output

Form structure

Record your result and evidence here or in a separate file.

Review gate

Every control has a programmatic label and the optional field is identified.

If the gate is not met

Use label and id associations rather than nearby text alone.

STAGE 2

Make validation useful

Native constraints can catch missing required values and email format, but custom rules may still be needed for whitespace-only names. Explain the error near the relevant field and preserve input. A user should know both what failed and how to fix it without interpreting an error code.

Your task

Add whitespace-name validation and visible correction guidance.

Required output

Validation behavior

Record your result and evidence here or in a separate file.

Review gate

A blank or whitespace-only name is refused; omitted email is allowed.

If the gate is not met

Align validation with the written required/optional policy.

STAGE 3

Support keyboard and assistive use

Use a logical DOM order, visible focus and native buttons. Group related choices with appropriate semantics. Error feedback should be discoverable without color alone. Automated inspection can catch missing attributes, but a keyboard walk-through is still needed to understand the interaction.

Your task

Complete the form using only the keyboard and record the focus order.

Required output

Accessibility review

Record your result and evidence here or in a separate file.

Review gate

All controls and the submit action are reachable with visible focus.

If the gate is not met

Remove custom interactions that duplicate a reliable native control without benefit.

STAGE 4

Handle local submission honestly

A local demonstration can validate and show a summary without sending data. Label that state clearly and avoid success wording that implies a real booking. Do not put form values in a URL or local storage unnecessarily. A real service would need server-side validation and a privacy-aware data flow.

Your task

Implement a local preview summary and a reset button.

Required output

Local-only interaction

Record your result and evidence here or in a separate file.

Review gate

No network request is made and reset clears the summary.

If the gate is not met

Inspect the submit handler and browser network log.

STAGE 5

Test realistic mistakes

Test empty submission, an invalid optional email, correction after error and a small viewport. Record observations rather than assuming that a clean screenshot means the form works. The learner’s test log should distinguish a self-review from sessions with actual participants.

Your task

Run the five-case checklist and revise one confusing instruction.

Required output

Usability evidence

Record your result and evidence here or in a separate file.

Review gate

The log contains actual observations and no invented participant feedback.

If the gate is not met

Mark planned tests as planned until performed.

Final project

Deliver the HTML form, validation logic, local-only summary and keyboard/mobile test log. Explain the extra work required before connecting a real submission endpoint.

Critical condition

Required rules match the labels and local preview is never represented as transmitted or booked data.

CriterionPointsEvidence
Evidence and correctness30Calculations, source use and results match the supplied case; limitations are honest.
Required artifacts30All five stage outputs and the capstone handoff are present and inspectable.
Reasoning and decisions20Choices, assumptions, alternatives and the case-specific critical condition are explained.
Reproducibility10A reviewer can follow the stated steps and distinguish expected from observed results.
Clear communication10Labels, units, structure and evidence references make the work easy to review.

Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.

Worked reference

The accepted local example is name Ada, no email and session morning. A whitespace-only name fails; an empty email passes because it is optional. The resulting summary says local preview and does not claim a reservation.

Boundaries

This is a local usability prototype, not a data-collection service or a complete accessibility certification.