Progress
Visual indicator for task completion. Supports linear bar and circular ring variants.
Overview
Purpose
The Progress component visual indicator for task completion. supports linear bar and circular ring variants.within our design system. It follows our primitive layer principles, ensuring consistency and reusability across applications.
When to Use
- Use when you need presenting information
- Appropriate for display contexts
- Follows primitive component patterns
When Not to Use
- Avoid when simpler alternatives exist
- Don't use for interactive functionality
- Consider alternatives for edge cases
Live Example
Anatomy
Understanding the structure of the Progress component helps ensure proper implementation and customization.
| Property | Description | Type |
|---|---|---|
| root | Slot rendered into [data-slot="progress"]. | Root |
| track | Slot rendered into [data-slot="progress-track"]. | Slot |
| fill | Slot rendered into [data-slot="progress-fill"]. | Slot |
| circleForeground | Circle foreground region of the component. | Part |
| indeterminate | Indeterminate region of the component. | Part |
| circle | Circle region of the component. | Part |
| circleBackground | Circle background region of the component. | Part |
| value | Slot rendered into [data-slot="progress-value"]. | Slot |
Variants & States
API Reference
Props
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
value | number | No | == undefined | — |
max | number | No | 100 | — |
variant | ProgressVariant | No | 'linear' | — |
size | ControlSize | No | 'md' | — |
intent | Intent | No | 'info' | — |
label | string | No | — | — |
showValue | boolean | No | false | — |
formatValue | (value: number, max: number) => string | No | — | — |
Accessibility
Standards Compliance
This component follows WCAG 2.1 AA guidelines and includes proper ARIA attributes, keyboard navigation, and screen reader support.
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 Progress component documentation. Found an issue or have suggestions?