practiceExperience & interface

Design QA

Design QA is the structured review of an implemented product against approved design intent, system rules, content, responsive behavior, and accessibility requirements.

Download Markdown (.md)

01What it means

Design quality assurance examines the built interface, not just design files. Designers, engineers, content specialists, and testers compare implementation with agreed behavior across states, viewports, input methods, and realistic data. The goal is not pixel worship; it is to find differences that harm clarity, consistency, accessibility, resilience, or the intended experience.[1][2][3]

Implementation checked against approved design intent Prepare criteria, inspect across states and viewports, fix findings, and verify again
  1. 01Prepare referenceIntent, system rules, content, states, and risks
  2. 02Inspect implementationResponsive layouts, platforms, data, and interaction
  3. 03Test accessibilityKeyboard, semantics, zoom, contrast, and assistive use
  4. 04Record findingsSeverity, evidence, expected behavior, and owner
  5. 05Fix collaborativelyResolve code, design, content, or system cause
  6. 06Verify + learnRetest and feed recurring issues into standards

Design QA complements code review, automated tests, accessibility evaluation, and user research; screenshot similarity alone is insufficient.

02Why it matters

Small implementation gaps accumulate into design debt: missing empty states, clipped translations, incorrect tokens, unusable focus order, inconsistent copy, or controls that behave differently across screens. A repeatable QA pass catches these problems before release and turns recurring discrepancies into improvements to components, acceptance criteria, and team workflow.

03When to use it

Run design QA continuously during implementation and again on a release candidate. Prioritize new patterns, high-risk journeys, responsive changes, accessibility-sensitive controls, and work that departs from the design system. A static happy-path comparison is insufficient for complex or data-dependent products.

04How it works

  1. Agree on the source of truth, supported environments, critical scenarios, and acceptance criteria before review.
  2. Inspect real builds with representative data across viewport sizes, zoom levels, themes, locales, and interaction states.
  3. Exercise keyboard, pointer, touch, focus, validation, loading, error, empty, and permission behavior where relevant.
  4. Log reproducible findings with evidence, expected behavior, severity, owner, and a link to the governing component or decision.
  5. Verify fixes in the build and feed repeated defects back into tests, documentation, tokens, and shared components.

05A practical example

Example

Before releasing a subscription upgrade flow, a team compares the staging build with the approved behavior. The review finds that long plan names wrap over prices, keyboard focus disappears after a modal closes, and the loading state changes button width. The team fixes the blockers, adds visual regression stories, and updates the modal component guidance.

06Where it breaks

Design QA cannot replace functional testing, user research, security review, performance testing, or formal accessibility evaluation. Visual diffs generate noise when rendering varies, and reviewers can over-prioritize cosmetic variance. The team needs severity rules so defects affecting task completion and inclusion outrank harmless pixel differences.

Common mistakes

  • Reviewing screenshots instead of interacting with the implemented states and transitions.
  • Checking only one viewport, one data shape, and the happy path.
  • Reporting vague mismatch comments without expected behavior, severity, evidence, or ownership.

07Sources

  1. Conformance Evaluation and ReportsW3C Web Accessibility Initiative · Standards guidanceConformance Evaluation and Reports
  2. Visual TestsStorybook · Technical documentationVisual Tests
  3. Testing for AccessibilityGovernment Digital Service · Government guidanceTesting for Accessibility
View saved topics

Start typing to search titles, definitions, categories, and frameworks.