Establish names and groups
Inspect persistent labels, instructions, required status, fieldsets, and the relationship between help text and each control.
Test form labels, instructions, validation, errors, keyboard use, browser zoom, and completion messages with observable checks.

Accessibility review should follow the respondent's task from the first instruction through error recovery and confirmation.
Inspect persistent labels, instructions, required status, fieldsets, and the relationship between help text and each control.
Complete the form by keyboard, check visible focus, and make sure menus, choices, and buttons work in a logical order.
Test browser zoom, narrow width, text spacing, and high contrast without losing content, controls, or the current answer.
Submit realistic mistakes, locate the summary, understand each message, correct the answer, and confirm that valid data remains.
Record what a tester can actually complete. A visual inspection or automated score alone is not a pass condition.
| Task | Test method | Pass evidence | Failure record |
|---|---|---|---|
| Understand each control | Compare visible labels with announced names | Names, groups, hints, and required states agree | Control, announced text, and mismatch |
| Complete without a pointer | Use keyboard from first field through submit | Focus stays visible and follows a usable order | Blocked action and last reachable control |
| Use a changed view | Test zoom, narrow width, and text spacing | Content and actions remain available without overlap | Viewport, setting, and obscured item |
| Recover from errors | Submit several realistic invalid values | Summary and field messages identify a repair | Rejected value, message, and lost data |
Decision: Release after the complete task, including error recovery and confirmation, has evidence from manual operation.
Accessible form design is the work of making the same task understandable and operable through different ways of seeing, hearing, moving, reading, and concentrating. It is not a final checklist applied after a form is built. Labels, grouping, instructions, validation, and recovery all affect the underlying structure.
The guides in this hub translate standards into observable tests. They show what to inspect in markup, what to attempt with a keyboard and zoom, what a useful error should say, and what a respondent needs after submission. They do not claim that one automated scan proves conformance.
For the most common failed state, use the detailed guide to accessible validation and error messages.
Apply the observable checks to the Web-Forms.net form builder before publishing an adapted field set.
A manual pre-publication review for names, grouping, instructions, errors, keyboard operation, zoom, and completion status.
Design accessible form validation with forgiving rules, connected error messages, useful summaries, preserved answers, and clear correction paths.
Write and test persistent form labels, group legends, hints, examples, and instructions that remain understandable with screen readers, speech input, and zoom.
Complete the form with a keyboard, zoom the browser, trigger every error, inspect focus, test a narrow layout, and confirm that the success state is announced and understandable.
The form owner owns the published result. New wording, required fields, conditional sections, colors, and third-party controls must be tested in the adapted form.
Let visitors report a barrier with enough context for the team to investigate.
Register learners and understand their starting point and support needs.
Register attendees and learn what each guest needs before the event.