Accessible Fields, Errors & Validation UX Make forms understandable to keyboard, screen-reader and sighted users
Phase 21 - Forms with React Hook Form + Zod Volume 06 - Professional Frontend
A form field is more than an input A production field needs a visible label, optional help text, an input control, and an error relationship that assistive technology can understand.
<div className={styles.field}>
<label htmlFor="title">Task title</label><input id="title" {...register("title")} aria-invalid={errors.title ? "true" : "false"} aria-describedby={errors.title ? "title-error" : undefined} />
{errors.title ? (
<p id="title-error" role="alert">
{errors.title.message}
</p>
) : null}
</div>Error UX rules Show errors next to the relevant field, use human language, preserve the user's input, and move focus or provide a summary when a large form fails in a way that would otherwise be difficult to discover.
aria-invalid on invalid fields Color-only error indication
aria-describedby to the error Unrelated error text with no relationship
role="alert" for newly appearing concise errors Dozens of noisy live regions
Client validation timing TaskFlow uses mode: "onBlur" for most field validation: the user can type without constant interruption, then receives feedback after leaving a field. Submission still validates everything.
A perfect client form does not secure an API. A caller can bypass the browser completely. NestJS must validate the transport request again.
Accessible Fields Errors and Validation UX matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Accessible Fields Errors and Validation UX” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: untrusted input → runtime schema → validated value → business rule → safe operation. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Create/edit task forms with shared field rules, accessible errors, async submission, server-error mapping, and reset behavior.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const CreateTaskSchema = z.object({
title: z.string().trim().min(1).max(160),
priority: z.enum(["LOW", "MEDIUM", "HIGH"]),
});
const input = CreateTaskSchema.parse(requestBody);Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Accessible Fields Errors and Validation UX” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Implement accessible field errors and focus behavior after invalid submit.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Showing only generic toast instead of actionable field errors
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.