A smart-home app's users with a large text-size setting see labels grow while icons stay tiny, breaking the pairing. How should a design system scale icons with text?
answer
- classify icons by what they pair with
- step through the size set
- fixed bars need a limit
- targets grow too
- test at the largest setting
basics
~20 sIcons paired with text should scale with it, stepping through the icon size set; icons in fixed bars grow with a limit; targets grow too, and layouts switch from side by side to stacked when enlarged content no longer fits.
solid answer
~50 sFirst I would **classify icons** by what they pair with. Icons that sit beside text, in list rows, labelled buttons and status lines, should **scale with the text**, stepping through the icon size set (or picking the matching optical variant) so strokes stay crisp and the pairing holds. Icons in fixed-space chrome, like a bottom navigation bar, can grow only **up to a limit**, because unlimited growth crowds or truncates the bar, so the label needs another path at large sizes. Large illustrative icons need not scale. **Targets grow** with their content, and layouts switch from side by side to stacked when enlarged content no longer fits. WCAG 2.2 1.4.4 Resize Text (AA) targets text, not icons, but clipped or overlapping icons are a loss of content. Finally, I would test every screen at the largest text setting.
go deeper
Recall that icons paired with text should grow when users choose a larger text size, so icon and label stay balanced.
Explain why scaling should step through the size set rather than use a continuous multiplier, and why targets must grow with enlarged content.
Demonstrate a classification of icons by role, a limit for fixed bars, layout changes at large sizes, and testing at the platform's largest setting.
Weigh consistent scaling rules across web and native mobile against per-surface judgement, deciding where the system fixes the rule and where teams decide.
## The symptom Most platforms let users choose a larger text size in their system settings. Apps that honour it enlarge their text, sometimes to well over twice the default. If the design system sizes icons in fixed units while text scales, the **pairing breaks**: in a smart-home control app, a room name grows to a large label while the lightbulb beside it stays at its small default size, the icon looks like a speck, and alignment between icon and first line of text is lost. The opposite failure is also common: everything scales without limit, and a bottom navigation bar overflows or truncates. ## Classify icons by what they pair with Not every icon should respond the same way. A design system's scaling rule is clearer when icons are grouped: | Icon role | Example | Scaling rule | |---|---|---| | Paired with text | Lightbulb beside a room name, icon inside a labelled button | Scale with the text, stepping through the size set | | Fixed-space chrome | Bottom navigation, a compact toolbar | Grow up to a limit, then change layout or labelling | | Standalone status | Signal or battery indicator in a device row | Scale with the row's text, since it is read alongside it | | Illustrative | Large picture on an empty state | Usually unchanged; it is not paired with text | ## Scale in steps, not continuously When an icon scales with text, the design system should map each text size to an **icon size from the set** rather than computing arbitrary values. Set sizes are the ones the drawings are tuned for, and where the system has optical size variants, stepping means the enlarged icon also gets the right drawing. A continuous multiplier produces sizes like 27.5 units that render soft and fall outside every review. Mechanically, each platform expresses this in its own terms: on the web by sizing icons in a text-relative unit, on native mobile by tying the icon to a scaled metric derived from the paired text style. The design-system rule is the same on both: *the icon follows its text style's size mapping*. ## Fixed bars need a limit A navigation bar has room for a fixed number of items. If each item's icon and label grow without bound, the bar either truncates labels or pushes items off screen. Common practice: - Let bar icons grow **modestly**, then cap them. - Provide the label another way at the largest sizes, for example a layout that shows it larger elsewhere, rather than letting it truncate. - Keep the bar's targets at least as large as before; capping the glyph never shrinks the target. ## Layout must adapt Scaling icons and text is only half of the work; layouts built for default sizes break under it: 1. **Targets grow** with their content, so hit areas stay comfortable around larger glyphs and labels. 2. **Side-by-side rows become stacked** when an icon, a label and a value no longer fit on one line, for example a thermostat tile that puts the reading below its label at large sizes. 3. **Labels wrap instead of truncating**, and icons stay aligned with the first line of wrapped text. ## Where the standards stand WCAG 2.2 success criterion **1.4.4 Resize Text** (Level AA) requires that, except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. It is about **text**; it does not require icons to scale. But a screen where enlarged text overlaps, clips or pushes icons out of view can lose content or functionality, which is exactly what the criterion forbids. Keeping paired icons in step with text is how design systems avoid that, and it preserves the visual pairing users rely on. ## Verifying it The rule is only as good as its testing. Review each template at the default size and at the platform's **largest** text setting, looking specifically for: - icons that stayed small beside large labels, - bars that truncate or overflow, - rows where icon and text lost alignment, - targets that stayed small around enlarged content.
- Should a bottom navigation bar's icons grow at the largest text sizes?Only up to a limit. The bar has fixed room for several items, so unlimited growth truncates labels or pushes items off screen. Common practice caps the glyph growth, keeps targets large, and gives the label another path at extreme sizes. Decide it per surface and test at the largest setting.
- Does WCAG 2.2 1.4.4 Resize Text require icons to scale with text?No. 1.4.4 (Level AA) requires text, except captions and images of text, to be resizable to 200 percent without assistive technology and without loss of content or functionality. Icons are not text, but if enlarged text clips or hides icons, content or functionality can be lost, so keeping paired icons in step is how systems stay safe.
saying these in an interview costs you the question
- Icons are graphics, so the text-size setting should never affect them.
- Every icon should scale without limit, navigation bars included.
- Multiplying icon size continuously keeps icons crisp at any setting.
- WCAG 1.4.4 requires every icon to scale to 200 percent.
- Testing screens at the default text size is enough.