Website UI Asset QA Checklist: How to Review Icons, Images, and Graphics Before Launch
UI designweb assetsdesign QAaccessibilitywebsite launch

Website UI Asset QA Checklist: How to Review Icons, Images, and Graphics Before Launch

PPicshot Editorial Team
2026-11-20
8 min read

Use this reusable UI asset QA checklist to review images, icons, SVGs, accessibility, responsive behavior, and dark mode before launch.

A website can look correct in a design file and still fail in production because an image crops badly, an SVG renders inconsistently, or an icon disappears in dark mode. This reusable UI asset QA checklist helps designers, developers, editors, and publishers review images, icons, and graphics before launch, document fixes clearly, and repeat the process after major interface changes.

Overview

UI asset quality assurance is the review of every visual file and its implementation context before users encounter it. The review is not limited to whether an image looks attractive. It also covers whether the correct file is used, whether it remains legible at different sizes, whether its information is available to assistive technology, and whether its behavior matches the surrounding interface.

Start by creating a simple inventory of the assets included in the release. Record the asset name, location, type, intended use, light or dark appearance, responsive behavior, and owner. This turns a visual review into a manageable design asset audit rather than a last-minute search through folders or a CMS.

For broader file organization guidance, see Design Asset Library Organization: Folder Structure, Naming Conventions, and Tracking Template. If the release includes a third-party icon set, also confirm its permitted usage and coverage using Best Free Icon Packs for Commercial UI Projects.

Core review categories

  • Appearance: Does the asset look sharp, balanced, and visually consistent with the interface?
  • Behavior: Does it crop, scale, load, and change correctly across breakpoints and states?
  • Accessibility: Can users understand the asset through suitable text alternatives, contrast, and clear context?
  • Technical delivery: Is the file format, naming, variant, and export appropriate for the implementation?
  • Library control: Is the approved source file easy to identify and is obsolete artwork excluded?

Checklist by scenario

Use the following review table as a release checklist. Mark each item as pass, fix, not applicable, or blocked. A blocked item should include the person or team needed to resolve it.

ScenarioWhat to checkEvidence of a pass
Responsive imagesReview the image at narrow, medium, and wide layouts. Check focal-point placement, object-fit behavior, aspect ratio, and text or faces near crop boundaries.The subject remains clear, no important content is cut off, and the selected image variant suits the component.
SVG graphicsOpen the SVG in the target interface and at several display sizes. Check viewBox dimensions, strokes, fills, clipping, and alignment.The graphic renders without missing paths, unexpected whitespace, or visibly uneven scaling.
IconsCompare icon size, optical alignment, stroke weight, corner treatment, and spacing with neighboring controls.Icons share a consistent visual language and do not appear too high, low, heavy, or small.
TransparencyPlace transparent PNGs, WebP files, and SVGs over light, dark, and tinted backgrounds.No unintended white box, halo, matte edge, or invisible detail appears.
Pixel densityInspect raster assets on standard and high-density displays or suitable previews. Confirm that export dimensions support the rendered size.Images and interface graphics remain crisp without unnecessary oversized files.
Names and locationsReview filenames, folder placement, CMS fields, and references in code or content records.Names describe purpose, variants are distinguishable, and the approved file is easy to trace.
Alt textDecide whether the image conveys information, supports a link or control, or is decorative. Review the text in context rather than in isolation.Meaningful images have concise descriptions; decorative images do not add distracting duplicate content.
ContrastCheck icons, text embedded in images, logos where applicable, focus indicators, and controls against their actual backgrounds.Important information remains distinguishable in every supported theme and state.
Loading variantsTest placeholder, low-quality, lazy-loaded, error, and fully loaded states where the component uses them.The layout does not jump unexpectedly and the fallback does not expose broken artwork or misleading content.
Dark modeReview logos, illustrations, photos, icons, shadows, borders, and transparent graphics in the dark theme.Assets remain visible, intentional, and brand-consistent without excessive glare or lost detail.

Review by breakpoint

Do not approve an asset from a single desktop screenshot. At minimum, review the smallest supported layout, a typical tablet or intermediate width, and the largest common layout. If the interface has a mobile navigation, card grid, or flexible hero section, test the transitions where the component changes structure.

For each breakpoint, capture the same component in its normal, hover or focus, disabled, loading, and error states when those states exist. Record the viewport, browser or device context, asset version, and observed issue. Consistent evidence makes it easier for a developer to reproduce the problem and prevents a fix for one layout from being mistaken for a complete fix.

What to double-check

Responsive crops and focal points

Choose images with a clear subject and enough surrounding space for the intended crop. A banner may need a different source image or focal-point setting from a card thumbnail. Check whether the CMS automatically crops, compresses, or generates variants, and confirm that its output does not remove the information the design depends on.

Also review captions, overlays, and text placed over images. A crop that looks acceptable on its own may create poor contrast once a gradient, headline, or button is added. For export and sizing guidance, refer to Web Image Optimization for Designers: Formats, Dimensions, and Export Settings.

SVG rendering and icon alignment

SVGs can be visually precise in a design application yet show unexpected spacing or color behavior in a browser. Check the actual implementation, not only the source preview. Look for an incorrect viewBox, strokes that become too thin at small sizes, fills that inherit an unintended color, and artwork that is not centered within its bounds.

Icon alignment should be judged optically as well as mathematically. A circular symbol and a square symbol can share the same bounding box but appear to sit at different heights. Compare icons beside labels and inside buttons, then adjust the asset or component rules consistently rather than applying isolated nudges without documentation.

Accessibility and contrast

Alt text should describe the purpose of an informative image, not list every visible detail. If an image is purely decorative and its meaning is already provided by nearby text, it should not create a second, confusing announcement. Images that function as links or controls need an accessible name that explains the destination or action.

Review contrast in the real layout, including cards, overlays, disabled-looking states, borders, and focus indicators. A contrast checker can support the review, but it does not replace judgment about whether an icon is recognizable or whether information is duplicated in color alone. The guide to Accessible Color Combinations for Brand and UI Design can help establish a repeatable color review process.

Filenames, variants, and ownership

Use names that identify purpose and variant without relying on vague labels such as “final-new” or “homepage-2.” A practical pattern might include the subject, component, theme, and revision when those distinctions matter. Keep source artwork separate from delivery files, and make the approved version obvious in the library or handoff.

For every replacement, document what changed: crop, color, dimensions, accessibility text, file format, or implementation instruction. This is especially important when a single asset appears in a website, newsletter, social template, or product interface. A clear handoff reduces the risk of a developer using an old file after the visual review is complete; see the Client Brand Asset Handoff Checklist for a related workflow.

Common mistakes

  • Checking only the design file: A source mockup does not reveal browser rendering, CMS transformations, loading states, or real content lengths.
  • Testing only the happy path: Review missing images, slow loading, empty states, long labels, and error messages as well as the fully loaded view.
  • Using one crop everywhere: Different components often need different aspect ratios and focal points.
  • Ignoring transparent edges: A subtle matte or halo may be invisible on the design canvas but obvious against a new background.
  • Treating filenames as an afterthought: Unclear names make duplicate or outdated assets more likely to enter the release.
  • Assuming light mode proves accessibility: Logos, icons, illustrations, and shadows can fail when the theme changes.
  • Writing alt text without context: A technically accurate description can still be redundant or fail to explain an image’s function.
  • Fixing symptoms locally: Repeated one-off offsets usually indicate an icon grid, export, or component rule that needs a shared correction.

Free UI kits and asset libraries deserve the same scrutiny as custom artwork. Before importing a set, review its formats, naming, licensing information, component coverage, and ability to support your themes and states. The checklist in How to Evaluate a Free UI Kit Before Using It is useful for that initial screening.

When to revisit

Run the complete checklist before a new website launch, redesign, major feature release, or migration to a different CMS. Repeat a focused review whenever a component changes its layout, a brand palette changes, a new theme is introduced, or the team replaces an icon or image library.

It is also worth scheduling a recurring audit before seasonal planning cycles and whenever design or development tools change. Export settings, browser behavior, image pipelines, and CMS capabilities can shift as workflows evolve. A twice-yearly review is a practical baseline for checking whether the process still reflects the tools and assets your team actually uses.

A practical closeout routine

  1. Export or collect the release asset inventory and assign an owner to each item.
  2. Test representative pages at supported breakpoints and in every available theme.
  3. Log each issue with a screenshot, viewport, asset filename, expected result, and priority.
  4. Replace or correct the source asset, implementation, alt text, or delivery variant.
  5. Re-test the original failure case and at least one related component.
  6. Archive superseded files and update the asset library, CMS record, or handoff notes.
  7. Record unresolved risks and schedule them for the next release rather than leaving them in informal messages.

Keep this checklist with the project’s release documentation. A short, repeatable review is more reliable than a large inspection performed only after visual defects reach production.

Related Topics

#UI design#web assets#design QA#accessibility#website launch
P

Picshot Editorial Team

Design Resources Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.