Field
Governs label/error associations for controls.
- Field (Composer)
Overview
Purpose
The Field component governs label/error associations for controls.within our design system. It follows our composer layer principles, ensuring consistency and reusability across applications.
When to Use
- Use when you need building form interfaces
- Appropriate for forms contexts
- Follows composer component patterns
When Not to Use
- Avoid when simpler alternatives exist
- Don't use for non-form contexts
- Consider alternatives for edge cases
Live Example
Anatomy
Understanding the structure of the Field component helps ensure proper implementation and customization.
Anatomy data not yet defined for this component. Define anatomy in the component contract file (Field.contract.json).
Variants & States
API Reference
Props
No props extracted. Props may be inherited or use complex types.
Accessibility
Standards Compliance
This component follows WCAG 2.1 AA guidelines and includes proper ARIA attributes, keyboard navigation, and screen reader support.
Common Pitfalls
- Duplicated logic in each input
- missing aria-describedby.
Accessibility Checklist
- ○ Keyboard navigation support
- ○ Screen reader compatibility
- ○ Color contrast compliance
- ○ Focus management
- ○ ARIA attributes
- ○ Reduced motion support
Usage Guidelines
✓ Do
- Use consistent spacing and sizing
- Follow established patterns
- Provide clear labels and descriptions
- Test with assistive technologies
✗ Don't
- Override core functionality
- Use without proper context
- Ignore accessibility requirements
- Modify without design system approval
Examples
Advanced Usage
Complex patterns including composition, state management, and real-world scenarios.
Development Tools
Use these tools to analyze the component's performance, design tokens, and accessibility during development.
Contribute
Help us improve the Field component documentation. Found an issue or have suggestions?