Materials and states
Match surface weight to structure, engagement, execution, and stacking.
Choose material from the control's job. Keep an input quiet, make the current working mode recognizable, and give a commit action more physical definition.
Material levels
| Material | Use | Treatment |
|---|---|---|
| Quiet structure | Inputs, cards, tables, toolbars, and inactive controls. | Neutral fill, a fine edge where needed, and no resting cast shadow. |
| Engaged | A selected view, mode, or important dataset filter. | Persistent selection with the carbon material family where stronger emphasis helps. |
| Execution | The action that commits or starts work. | A tactile gradient, directional border lighting, and restrained shadow. |
| Elevated | A menu, popover, dialog, or drawer above the workspace. | A distinct floating surface and shadow that communicates stacking. |
Keep structural cards and fields planar. Use the protected execution recipe for primary actions rather than approximating its gradient or lighting.
Actions and modes
Primary and optional accent solid buttons use the tactile treatment. Secondary solid actions stay flat. Use outline and ghost treatments for actions that need less emphasis.
Structural tabs identify a section through text and a fine indicator. Contained tabs can use a quiet track. Working modes such as Grid/List or Preview/Code need a persistent selected treatment so someone can recognize how the interface currently operates.
Checkboxes, radios, and switches need clear checked states and visible focus. A selected row can use an informational tint when that helps scanning.
Interaction states
| State | What to preserve |
|---|---|
| Hover or focus | Immediate feedback and a visible keyboard target. |
| Pressed | A short physical response without changing the control's layout. |
| Selected or editing | Persistent engagement that remains recognizable after the pointer leaves. |
| Loading | Stable dimensions, progress information, and protection against duplicate actions. |
| Disabled | A clear unavailable state with no competing hover or press treatment. |
| Error | A description of the problem and the action needed to recover. |
Principles defines how overlapping states take priority. Keep outcome messaging available when focus or selection also matters.
Overlays
Use a menu for commands, a popover for nearby context, a dialog for a focused interruption, and a drawer for a side task. Provide a title or accessible name, a clear dismissal path, and focus return where appropriate.
Keep tooltip content informational. Put actions in a surface that supports interaction. Give the floating surface enough elevation to separate it from the workspace, without glow or default glass effects.