Input
Single-line text entry.
- Input (Text, Number, Password)
- Text Input
- Input field
- Input field with button
- Input text
- Input: text
- Text input field
- Text field wrapper
- Text field
- Textfield
- Form Input
- Text Box
- Entry Field
- Data Entry
Overview
Purpose
The Input component single-line text entry.within our design system. It follows our primitive layer principles, ensuring consistency and reusability across applications.
When to Use
- Use when you need collecting user input
- Appropriate for inputs contexts
- Follows primitive component patterns
When Not to Use
- Avoid when simpler alternatives exist
- Don't use for display-only content
- Consider alternatives for edge cases
Live Example
Anatomy
Understanding the structure of the Input component helps ensure proper implementation and customization.
| Property | Description | Type |
|---|---|---|
| root | Slot rendered into [data-slot="input"]. | Root |
Variants & States
API Reference
Props
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
invalid | boolean | No | {aria | — |
Accessibility
Standards Compliance
This component follows WCAG 2.1 AA guidelines and includes proper ARIA attributes, keyboard navigation, and screen reader support.
Common Pitfalls
- Mixing label/error inside
- missing aria-\*
- inconsistent disabled/required.
Accessibility Checklist
- ○ Keyboard navigation support
- ○ Screen reader compatibility
- ○ Color contrast compliance
- ○ Focus management
- ○ ARIA attributes
- ○ Reduced motion support
Content Guidelines
Voice
Helpful and guiding
Tone
Clear and supportive
Copy Examples
Enter your email address
Password (minimum 8 characters)
Pass
UI Copy Patterns
- Use descriptive labels, not placeholders
- Include format hints when needed
- Provide clear error messages
- Use helper text for complex inputs
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.
Changelog
- addedAdded `success` prop for success state styling
- changedImproved error state visual feedback
- addedInitial release of Input component
Contribute
Help us improve the Input component documentation. Found an issue or have suggestions?