You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 2nd-gen/packages/swc/components/progress-circle/ProgressCircle.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ import styles from './progress-circle.css';
27
27
/**
28
28
* Progress circles show the progression of a system operation such as downloading, uploading, processing, etc. in a visual way.
29
29
*
30
-
* They can represent determinate (with a specific progress value) or indeterminate (loading) progress.
30
+
* They can represent determinate (with a specific progress value) or indeterminate (loading) progress. If no `progress` value is given, the progress circle is indeterminate.
// @todo Blurring the range control seems to cause a catastrophic Storybook render failure, so using number input for now. React spectrum has the range control working, check their implementation for a solution.
@@ -291,12 +285,13 @@ export const ProgressValues: Story = {
291
285
* - Use specific, meaningful labels (e.g., "Uploading profile photo" instead of "Loading")
292
286
* - Use determinate progress (`progress="50"`) when possible to give users a clear sense of completion
293
287
* - For determinate progress, ensure the `progress` value accurately reflects the actual progress
294
-
* - Use indeterminate progress only when duration is truly unknown
288
+
* - Use indeterminate progress only when duration is truly unknown or when the wait is less than 3 seconds.
295
289
* - Consider using `size="l"` for primary loading states to improve visibility
296
290
* - Ensure sufficient color contrast between the progress circle and its background
297
291
* - Use `static-color="white"` on dark backgrounds or `static-color="black"` on light backgrounds
298
292
* - Test with screen readers to verify progress announcements are clear and timely
299
293
* - Avoid updating progress values more frequently than every 1-2 seconds to prevent announcement overload
294
+
* - Do not force live region announcements for progress durations that are 3 seconds or less. Instead, consider status messages when progress is complete or there is an error
0 commit comments