Accessibility, Keyboard & Focus Architecture Build WCAG 2.2 thinking into component behavior and semantics
Phase 20 - Production Application UI Volume 06 - Professional Frontend
v
v
v
v
Phase 20 turns the secure full-stack foundation into a coherent, accessible application interface without moving business authority into the browser.
Accessibility is component architecture TaskFlow targets WCAG 2.2 AA thinking from the beginning. The goal is not a “compliance page” at the end; keyboard behavior, focus, labels, semantics, target size, reflow, and error communication influence how components are designed.
Focus Visible `:focus-visible`; no sticky UI fully hides focus
Bypass Skip link to `#main-content`
Target size Primary controls designed around >=44px comfort; never crowd tiny targets
Zoom/reflow Test at narrow widths and 200% zoom
Why 24px and 44px both appear in accessibility discussions WCAG 2.2 AA introduces a 24x24 CSS pixel minimum target-size criterion with exceptions. A 44x44 target is the stronger enhanced target and remains a practical design goal for primary controls, especially touch interfaces.
v
v
v
v
v
Focus order should follow the visual and semantic reading order.
Do not remove outlines without replacing them. WCAG 2.2 requires keyboard focus to be visible and adds requirements around focus not being obscured by authored content.
Accessibility Keyboard and Focus Architecture 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 “Accessibility Keyboard and Focus Architecture” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: route data → UI state → component tree → interaction → accessible feedback. 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: TaskFlow responsive shell with navigation, workspace context, task screens, loading/empty/error states, and accessible interactions.. 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.
if (query.isPending) return <TaskSkeleton />;
if (query.isError) return <TaskError retry={query.refetch} />;
if (!query.data.length) return <EmptyTasks />;
return <TaskTable tasks={query.data} />;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 “Accessibility Keyboard and Focus Architecture” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Design the application shell first: sidebar/topbar/main content/mobile navigation.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Clickable divs without keyboard semantics
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.