What it does
Pair visuals with aria-valuenow updates for assistive technologies.
Avoid fake progress that stalls—users lose trust quickly.
Composition and API
Prefer compound subcomponents instead of one oversized prop bag. Export a small, documented API for your design system.
Reset to indeterminate spinners when duration is unknown.
Common use cases
- File uploads with byte counts and ETA copy.
- Checkout steps with weighted segments.
- Background sync jobs in admin consoles.
- Onboarding checklists tied to measurable tasks.
Accessibility
Keyboard order, focus rings, and ARIA attributes should match production usage. Test with your supported browsers and assistive technologies when semantics are non-trivial.
This preview page exposes a single h1 in the hero for a clean outline.
Next.js integration notes
Colocate examples under the App Router, keep server and client boundaries explicit, and avoid pulling interactive overlays into unexpected server layouts.
Set NEXT_PUBLIC_SITE_URL so canonical and Open Graph URLs resolve on deploy.
FAQ
Does the Progress component work with Next.js App Router?
Yes. Import it like any other React component; keep interactive subtrees in client components when you need hooks or browser APIs, and leave static structure in server components where possible.
Can I customize progress with Tailwind CSS?
Zentauri UI exposes class-friendly variants and slots so you can extend styles with Tailwind utilities without fighting inline styles.
Is this Progress implementation accessible by default?
Primitives follow sensible defaults, but accessibility depends on how you label controls, manage focus, and wire keyboard handlers in your app. Validate critical flows with keyboard-only use and screen readers.