A reliable UI icon audit catches visual inconsistencies, accessibility gaps, and export problems before they reach a website, app, or design system. Use this reusable checklist to review icons in Figma, inspect exported SVG files, and confirm that each icon is ready for production.
Overview
An icon audit is more than a quick visual scan. A set can look polished while still containing uneven stroke weights, unclear names, inaccessible controls, oversized files, or SVG markup that is difficult to maintain. Reviewing these details together helps designers and developers ship an icon library that feels consistent and behaves predictably.
Start by defining the intended use of the set. Icons used beside text in a dashboard may need different optical sizing from icons used as large empty-state illustrations. A navigation icon, a decorative graphic, and an icon-only button should not automatically share the same implementation or accessibility treatment.
Keep four questions in view during the audit:
- Does the set look consistent? Check geometry, alignment, proportions, corner treatment, and stroke behavior.
- Can people understand and operate it? Check contrast, touch or click areas, labels, and nonvisual meaning.
- Can the team maintain it? Check names, component structure, variants, and documentation.
- Will it work in production? Check SVG structure, rendering, scaling, performance considerations, and handoff details.
For broader accessibility considerations across icons, illustrations, and marketing graphics, use the Accessible Design Asset Checklist alongside this icon-specific review.
Checklist by scenario
1. Reviewing visual consistency in a design file
Place the complete set on one page at the same displayed size. Looking at icons together makes differences easier to spot than reviewing them one at a time.
- Grid alignment: Confirm that the artwork uses the intended viewBox and aligns to the established keyline or grid. Inspect the edges as well as the center; an icon can be mathematically centered but still look visually off-balance.
- Stroke weight: Compare the nominal stroke width, cap style, join style, and outline behavior. Check whether strokes remain coherent at the sizes where the icons will actually appear.
- Optical sizing: Adjust for visual mass rather than forcing every path into identical boundaries. A dense calendar may need a different apparent size from a simple plus sign.
- Proportions: Look for recurring relationships between outer shapes, counters, gaps, and corner radii. One icon with unusually narrow or wide internal spacing can make the whole set feel uneven.
- Filled and outlined styles: If the library includes both, define when each style is used. Do not mix them in the same control without a clear state or hierarchy rule.
- State behavior: Review default, hover, focus, selected, disabled, loading, and error states where applicable. States should communicate change without relying on color alone.
2. Reviewing an icon component in a design system
- Naming: Use names based on meaning or function rather than appearance alone. A name such as “arrow-right” describes shape; a name such as “next” may describe a context. Choose one naming approach and document it.
- Variants: Define size, style, orientation, and state properties consistently. Remove unnecessary combinations that could confuse designers or developers.
- Usage guidance: Document when to use the icon, what it should not replace, and whether it may appear without visible text.
- Alignment rules: Specify how the icon sits beside text, inside a button, or within a navigation item. Include spacing guidance so each product team does not solve the same problem differently.
- Deprecation: Mark replaced icons clearly and provide a migration path. Avoid silently changing the meaning or shape of an existing icon that may already be familiar to users.
3. Reviewing an icon-only control for accessibility
- Purpose: Confirm that the action is understandable from its accessible name, surrounding context, or both.
- Screen-reader labeling: Make sure an icon-only button or link receives a meaningful label in the implementation. Decorative icons inside a labeled control should not create a duplicate announcement.
- Visible alternatives: Use visible text where the action may be ambiguous, unfamiliar, or high consequence. A tooltip can support discovery but should not be the only reliable source of meaning.
- Contrast: Test the icon against its actual background and in each relevant state. If the icon communicates status, pair color with text, shape, position, or another distinguishable cue.
- Interaction area: Verify that the clickable or tappable region is large enough for the product context and does not depend on the visible path boundary alone.
- Keyboard and focus behavior: Confirm that the control can be reached and that its focus indication remains visible and distinct.
4. Reviewing exported SVG files
- ViewBox: Confirm that every file has the expected viewBox and scales without unexpected cropping or extra whitespace.
- Structure: Look for unnecessary groups, hidden layers, embedded raster images, masks, clipping paths, or editor-specific metadata that the product does not need.
- Paint attributes: Decide whether color belongs in the SVG or should be controlled by the interface. A currentColor-based approach may be useful for adaptable interface icons, but use the implementation pattern that matches the system.
- Path behavior: Check whether strokes are intentionally preserved or converted to paths. Conversion can improve predictability in some workflows but may make later editing harder.
- IDs and accessibility metadata: Avoid duplicate or unstable identifiers when they could create conflicts. Decide whether the file itself needs a title or description, or whether the containing component will provide the accessible name.
- Rendering: Open the exported files in the target browsers, operating systems, and interface states. Compare them with the source file at small, normal, and enlarged sizes.
What to double-check
| Audit area | Pass condition | Evidence to record |
|---|---|---|
| Geometry | Keylines, proportions, corners, and internal gaps follow the set rules. | Annotated comparison board or review notes. |
| Stroke | Weight, caps, joins, and alignment are intentional across related icons. | Representative small, medium, and large-size samples. |
| Optical balance | Icons appear balanced, not merely mathematically centered. | Side-by-side review at actual interface sizes. |
| Accessibility | Meaning, contrast, focus, interaction area, and labeling are defined. | Component examples and implementation notes. |
| File quality | SVGs scale, render, and contain only necessary structure. | Export inspection and browser or platform checks. |
| Library management | Names, versions, categories, and deprecations are documented. | Library index or component metadata. |
In Figma, begin with the source components rather than detached copies. Review the master component, its variants, and its published name. Then create a simple inspection page containing the full set, common pairings, and controls at their intended display sizes. Use overlays or duplicate frames to compare revisions. Before handoff, export a representative sample and inspect the actual SVG output instead of assuming the export matches the canvas.
For file organization and naming practices that extend beyond icons, see the guide to building a reusable design asset library. If the icons are part of a larger brand handoff, also review the design asset licensing and client handoff checklist.
Common mistakes
- Checking only the master grid: An icon may align correctly in the design file but render with excess whitespace or a different baseline after export. Inspect the delivered file.
- Making every icon the same box size: Equal frames do not guarantee equal visual weight. Use optical adjustments where necessary and document exceptions.
- Using color as the only status cue: Pair color with a label, shape, position, or other perceivable change.
- Adding labels only at the end: Accessibility naming is part of component design, not a final decoration. Define it while the interaction is being designed.
- Testing only at a large size: Gaps, counters, and thin strokes can fail at the actual interface size. Review the smallest intended use first.
- Over-cleaning the SVG: Removing every group or attribute without understanding the implementation can break styling, masks, or accessibility behavior. Simplify deliberately and retest.
- Changing familiar icons without migration notes: A visually improved icon can still create confusion if its meaning, placement, or interaction changes without communication.
When to revisit
Run this UI icon audit before a new product release, design-system publication, major navigation change, or bulk import of downloaded design assets. Recheck the set when the product adds a new platform, theme, density, localization requirement, or interaction pattern. A seasonal planning cycle is also a practical time to review unresolved exceptions and remove obsolete icons.
Revisit the checklist whenever Figma, your export tooling, browsers, operating systems, or component framework changes in a way that could affect rendering or implementation. Accessibility guidance and product requirements can also change, so confirm the criteria your team is expected to meet rather than treating an old pass as permanent.
For a practical final pass, assign one reviewer to inspect visual consistency and another to test implementation behavior. Record each issue with the icon name, scenario, severity, screenshot or file reference, and owner. Fix the highest-impact problems first: incorrect meaning, inaccessible controls, broken rendering, and inconsistent system rules generally deserve attention before minor optical refinements. Then update the source component, exported asset, documentation, and audit date together. That habit turns an icon audit from a one-time cleanup into a repeatable part of production readiness.