Loader
Design System - Loader component
The Loader component is a fundamental UI element. It visually communicates ongoing processes such as data fetching, form submission, or navigation transitions. The loader helps set user expectations by indicating that a background action is in progress, reducing uncertainty and improving perceived performance.
// Sample code
<CheckBox
label="Label"
onChange={(e)=>{console.log(e.target.checked}}
/>Anatomy
Variants
Default
A simple spinner with optional loading text. Typically used for inline or section-based loading indicators.
Page Loader
A fullscreen loader that appears during full-page transitions or major data loads, ensuring users are aware of system-level activity.
Overlay Loader
Appears over existing content with a dimmed background. Ideal for actions like uploading media or submitting forms, preventing user interaction during processing.
Properties
Loader Text
Optional text (e.g., "Loading...") can be displayed alongside the spinner to clarify the ongoing process for the user.
Property Configuration Table
Each design component offers a range of configurable options. These options are intentionally platform-agnostic, allowing implementations to adapt and tailor them to align with the specific requirements of the chosen framework.
variant
text
className
text
style
yes/no
no
loaderText
yes/no
no
animationStyles
number
Behaviours
Blocks Interaction
While the loader is active, especially in page or overlay mode, user interaction is restricted to avoid conflicting inputs during processing.
Auto Dismiss
Loaders are dismissed automatically upon completion of the associated process, ensuring smooth transitions and minimising wait perception.
Usage Guide
Use loaders for content that is loading
Use medium or large loaders for content that is loading in large areas, without space constraints, such as web pages, panels, or dashboards.
Avoid using small loaders for full-page or overlay loading, as they may not be noticeable or may seem visually unbalanced.
Changelog
Dec 15, 2024
v-0.0.2
This component is added to the website. This component is now individually versioned.
Design Checklist
All interactive states - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
Accessible use of colours - Colour is not used as the only visual means of conveying information (WCAG 2.1 1.4.1)
Accessible contrast for text - Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).
Accessible contrast for UI components - Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).
Keyboard interactions - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
Screen reader accessible - All content, including headings, labels, and descriptions, is meaningful, concise, contextual and accessible by screen readers.
Responsive for all breakpoints - Responsiveness for 3 breakpoints - Mobile, Tablet and Desktop
Usage guidelines - Includes a list of dos and don'ts that highlight best practices and common mistakes.
Writing guidelines - Content standards and usage guidelines for writing and formatting in-product content for the component.
Defined variants and properties - Includes relevant variants and properties (style, size, orientation, optional iconography, decorative elements, selection states, error states, etc.)
Defined behaviours - Guidelines for keyboard navigation and focus, layout management (including wrapping, truncation, and overflow), animations, and user interactions.
Design Kit - Access to the design file for the component in Figma, multiple options, states, colour themes, and platform scales.
Last updated
Was this helpful?