Build and review a small semantic HTML form with labels, useful validation and a clear local-only submission state.
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.
| Field | Required | Rule |
|---|---|---|
| Name | yes | nonblank |
| no | email format if supplied | |
| Session | yes | choose morning or afternoon |
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.
Create the three-field semantic form.
Form structure
Record your result and evidence here or in a separate file.
Every control has a programmatic label and the optional field is identified.
Use label and id associations rather than nearby text alone.
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.
Add whitespace-name validation and visible correction guidance.
Validation behavior
Record your result and evidence here or in a separate file.
A blank or whitespace-only name is refused; omitted email is allowed.
Align validation with the written required/optional policy.
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.
Complete the form using only the keyboard and record the focus order.
Accessibility review
Record your result and evidence here or in a separate file.
All controls and the submit action are reachable with visible focus.
Remove custom interactions that duplicate a reliable native control without benefit.
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.
Implement a local preview summary and a reset button.
Local-only interaction
Record your result and evidence here or in a separate file.
No network request is made and reset clears the summary.
Inspect the submit handler and browser network log.
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.
Run the five-case checklist and revise one confusing instruction.
Usability evidence
Record your result and evidence here or in a separate file.
The log contains actual observations and no invented participant feedback.
Mark planned tests as planned until performed.
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.
Required rules match the labels and local preview is never represented as transmitted or booked data.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, 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.
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.
This is a local usability prototype, not a data-collection service or a complete accessibility certification.