A business form should identify the problem, explain how to correct it and preserve valid work. After Save, distinguish an operation in progress, a confirmed save and an uncertain result that needs checking. A red border or short-lived notification alone is not enough to help someone finish the task.
Key points: connect field-level messages with an error summary, define what input survives a failure and specify save states separately. Start by testing one order-entry flow with a keyboard, a small screen, a failed request and repeated submission. Adapt the examples below to your product; they do not constitute a complete WCAG conformance assessment.
[01]Identify the field and explain the error in text
'Check your input' does not tell the user what to change. In a hypothetical order form, name the field, such as 'Enter a delivery date', and show any applicable date restriction. The order flow and copy in this article are illustrative examples, not reported client cases.
WCAG 2.2 Error Identification requires automatically detected input errors to identify the affected item and describe the error in text. It does not prescribe a single display location or presentation. A red border can supplement the explanation, but cannot replace it.
- Label: use the same field name in the label and the error message.
- Reason: distinguish missing values, format errors, allowed ranges and business conflicts.
- Next action: distinguish a value the user can correct from a problem requiring an owner's review.
[02]Separate input errors from system failures
The following copy matrix is a BOYD recommendation to adapt after checking business rules and server responses. If stock has changed, calling it a number-format error can send the user into repeated edits. Avoid exposing internal error codes or server details that do not help the user recover.
| Situation | Suggested message | Next action |
|---|---|---|
| Required delivery date missing | 'Enter a delivery date' | Go to the field |
| Quantity outside the allowed range | State the allowed range and unit | Edit the current input |
| Another user changed the order | Explain the conflict and need to inspect the latest version | Preserve the draft and compare |
| Submission result unknown | Say that saving could not be confirmed | Check the result before retrying |
| Save confirmed | Identify the saved record and completed state | Offer record details or the next task |
A business conflict may require the server's current state. Instead of offering only Retry, define available paths such as copying a draft, checking the latest record or contacting an owner. Do not silently change amounts or stock values; make the change visible for review.
[04]Distinguish recovery from long-term draft storage
Design so that one invalid field does not erase the customer, address and order lines. For multi-step flows, specify what survives Back navigation, whether attachments need uploading again and what happens on session expiry. This does not mean retaining sensitive data indefinitely in the browser.
WCAG 2.2 Redundant Entry addresses information already entered or provided earlier in the same process: if needed again, it should be auto-populated or available for selection. Exceptions cover essential re-entry, security needs and information that is no longer valid. It does not require long-term autosave for every form.
BOYD recommends documenting error recovery separately from a persistent draft feature. Persistent drafts need decisions about storage, access, retention, shared devices and deletion. If some input cannot survive a failure, explicitly state the remaining task, such as selecting an attachment again.
[05]Distinguish saving, saved and uncertain outcomes
Do not make a loading indicator the only evidence of completion. BOYD recommends distinguishing confirmed success from a lost response with an unknown result. A confirmed order can link to its details; an uncertain result can offer a lookup path before another submission.
WCAG 2.2 Status Messages addresses status information such as results, progress and errors that appears without receiving focus, so assistive technology can present it. Visible text and an announced update are separate checks. Choose roles and properties for the message's purpose instead of treating every update as an urgent alert.
Disabling repeat clicks is not proof that duplicate saves are impossible. Define request identifiers, server-side duplicate control and result lookup with engineering. The interface guides the next action; the connected system must verify whether an operation is applied once.
[06]Include failure scenarios in design acceptance
Do not accept a form design using only its happy path. Prepare normal, missing-input, server-validation, concurrent-edit, network-failure and completed states for one form so the team can discuss concrete behavior. These questions are a starting point; further checks should use the actual assistive technology and operating environment.
- Can a keyboard user complete input, submission, error discovery, correction and resubmission?
- Are summaries, messages and fields visible on a small screen and under magnification?
- Does valid input survive failure, with explicit instructions for anything that must be re-entered?
- Are success and uncertainty distinguished, with server results checked for duplicate submissions?
- Do deliverables cover copy, error mapping, focus, preserved input and review ownership?
For a redesign discussion, bring a de-identified sample and one frequently failing workflow rather than live personal data. Map current states and business rules before choosing what to reuse as components. Assess the effect of changes through actual usability checks and operational observation.
- Form UX
- Error recovery
- Accessibility
- Business interfaces





