Field validation and form feedback
Inline errors, summaries, warnings, server conflicts, success confirmation and focus-to-error behavior.
Shared componentFuture Spec 16 →Current-state summary
Field validation and form feedback appears across the current product but is not yet governed as one fully documented reusable component. Required labels are common, but cross-field errors, server conflicts, mapping errors, focus-to-first-error and submission summaries are not one reusable system.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Canonical interaction | Validate on appropriate blur/change and always on submit; avoid premature errors while typing. Show inline error plus top summary for long forms and move focus to the summary/first invalid field. Distinguish error, warning and informational guidance; server response maps to stable field keys and preserves entered values. | Required reusable contract |
| Data contract | Validation results use stable codes, field keys, severity and safe message parameters; do not rely on English text for logic. | Required shared storage and API behavior |
| Accessibility | Invalid fields use aria-invalid and described error text; summaries link to fields and errors are announced after submission. | Required before component is approved for reuse |
| Reuse inventory | all forms, builders, imports, commercial documents, Application review, integrations | Known current and future consumers |
| Current inconsistencies | Application mappings can be wrong without blocking publish. Long modal validation behavior is unclear. Optimistic concurrency conflicts are not represented. | Observed or identified correction work |
User journeys
Current flows
Use Field validation and form feedback
- Render from the shared component registry
- Load canonical value and configuration
- Accept keyboard, pointer or assistive-technology input
- Validate and normalize
- Persist canonical value with provenance
- Render the same meaning in profiles, grids, filters, exports and integrations
State model
Current and expected states
Value can be entered or selected with a visible label.
Must provide a visible focus indicator without layout shift.
Must distinguish unavailable input from view-only canonical value.
Requirement is communicated in label, schema and validation—not colour alone.
Inline message explains the problem and preserves the user’s input where safe.
Async work prevents duplicate commands and remains announced.
Null, empty string, zero and empty collection retain distinct meanings.
Product rules
Non-negotiable boundaries
- Build once and reuse the same component, schema and formatter in every Workspace experience.
- Display formatting is separate from canonical storage.
- Every value has a stable field key, type, validation, privacy classification and version.
- Client validation improves usability; server validation remains authoritative.
- Equivalent values render consistently in forms, grids, profiles, filters, exports, notifications and documents.
- Validate on appropriate blur/change and always on submit; avoid premature errors while typing.
- Show inline error plus top summary for long forms and move focus to the summary/first invalid field.
- Distinguish error, warning and informational guidance; server response maps to stable field keys and preserves entered values.
Known current limitations · 3 mapped
What is missing, broken or unverified
Future Spec 16 owns closure →- Application mappings can be wrong without blocking publish.
- Long modal validation behavior is unclear.
- Optimistic concurrency conflicts are not represented.
Future alignment
Required evolution
- 01Promote this pattern into the approved component library.
- 02Replace local copies incrementally and retain migration adapters only where required.
- 03Add automated interaction, validation, accessibility and serialization tests.
- 04Track reuse across: all forms, builders, imports, commercial documents, Application review, integrations.
Current baseline
Acceptance record
- The component has one public API and canonical data contract.
- All required states are documented and tested.
- Formatting and validation are consistent across every consumer.
- Keyboard and screen-reader testing passes.
- Existing inconsistent copies have an owner and migration plan.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented