Overview
Design QA goes beyond visual review to ensure products are usable, accessible, consistent, performant, and meet specifications across all contexts.
Responsive Design Testing
### Breakpoint Validation
- Test at documented breakpoints (mobile: 375px, tablet: 768px, desktop: 1440px)
- Verify layout adapts correctly at each breakpoint
- Check component spacing and sizing adjustments
- Ensure text remains readable at all sizes
- Test between breakpoints for reflow issues
### Mobile-First Review
- Start testing at smallest viewport first
- Verify touch targets minimum 44x44px
- Check vertical scroll experience without horizontal scroll
- Test all interactions at mobile size
- Validate modal and overlay behavior
- Review navigation pattern for mobile context
### Tablet and Landscape Testing
- Test at common tablet sizes (iPad, Android tablets)
- Review landscape orientation layouts
- Verify sufficient padding and margins
- Check two-column layouts work at tablet width
- Test split-view scenarios (email/detail on iPad)
### Desktop and Large Display
- Test at minimum and maximum supported widths
- Verify content width and line lengths (50-75 characters optimal)
- Check spacing doesn't feel excessive at large sizes
- Validate that stretched images don't distort
- Review navigation patterns for screen real estate
Accessibility Testing
### Color Contrast
- WCAG AA: 4.5:1 for normal text, 3:1 for large text
- WCAG AAA: 7:1 for normal text, 4.5:1 for large text
- Test with contrast checker tools
- Check background vs. text colors
- Verify focus indicators have sufficient contrast
- Test on various backgrounds, not just white
### Keyboard Navigation
- Tab through entire interface in logical order
- Verify all interactive elements are focusable
- Check focus indicators are visible and clear
- Test keyboard shortcuts for consistency
- Verify no keyboard traps (can't escape focus)
- Validate form navigation and submission
### Screen Reader Testing
- Use NVDA, JAWS, or VoiceOver to test
- Verify headings are properly structured (H1 > H2 > H3)
- Test alternative text on images describes content
- Validate form labels associated with inputs
- Check hidden elements marked appropriately
- Test link text makes sense out of context
### Semantic Structure
- Verify proper heading hierarchy without skipping levels
- Validate list structure for navigation and content
- Test form structure with label, input, error message relationships
- Check table headers and associations
- Verify landmarks used (main, nav, aside, footer)
Cross-Browser Testing
### Browser Compatibility Matrix
- Chrome/Edge (Chromium-based): Latest 2 versions
- Firefox: Latest 2 versions
- Safari: Latest 2 versions (macOS and iOS)
- Test interaction patterns, animations, gradients
- Verify CSS and layout rendering consistency
### Rendering Verification
- Check typography rendering across browsers
- Verify shadow and gradient quality
- Test animation smoothness and performance
- Check transparency and blend modes
- Validate form input styling and behavior
### Feature Detection
- Test features that might not be supported uniformly
- CSS Grid, Flexbox, custom properties
- Backdrop filters, mix-blend-mode
- Modern font features (variable fonts)
- Verify graceful degradation if unsupported
Performance and Visual Quality
### Image Quality
- Verify images don't appear blurry or pixelated
- Check image dimensions match intended size
- Test responsive image sizes (srcset)
- Validate retina/2x display rendering
- Review image compression doesn't degrade quality
### Animation Performance
- Test animations remain smooth (60fps target)
- Verify no jank or stuttering
- Check animation duration and timing feel natural
- Validate animations complete without hanging
- Test on various device performance levels (throttle CPU)
### Loading States
- Verify all loading indicators appear promptly
- Test skeleton screens and placeholders
- Check error states display appropriately
- Validate timeout handling and messaging
- Test network throttle scenarios
Consistency Verification
### Design System Compliance
- Verify spacing follows grid system
- Check typography uses defined sizes and weights
- Validate colors match design system palette
- Confirm components use approved patterns
- Check for any ad-hoc styling that bypasses system
### Component Consistency
- Test buttons look and behave consistently
- Verify form inputs are uniform across product
- Check card layouts maintain consistent spacing
- Validate modal and dialog styling
- Review header/footer consistency
### Brand Consistency
- Verify brand colors are correct and consistent
- Check logo usage and sizing
- Validate typography matches brand guidelines
- Review imagery style and tone
- Check overall visual cohesion
Content and Copy Review
### Typography Quality
- Check for orphaned words (single word on new line)
- Verify no excessive hyphenation
- Test long content without line breaks
- Check punctuation and spacing (em dashes, ellipsis)
- Review line lengths for readability (50-75 chars optimal)
### Placeholder and Error Content
- Test all error message states display correctly
- Verify placeholder text provides helpful guidance
- Check empty states have meaningful messaging
- Test very long content in input/output areas
- Validate special characters display properly
### Copy Length and Translations
- Test content at different text lengths
- Verify layouts work with longer text (translations)
- Check right-to-left language support if applicable
- Test multi-line content behavior
- Validate truncation with ellipsis appropriate
Form and Interaction Testing
### Form Validation
- Test required field validation
- Verify error messages appear near relevant fields
- Check success states after submission
- Test field-level validation on blur/change
- Validate form state preservation on error
### Button and Link Behavior
- Verify disabled buttons appear appropriately
- Test loading/processing button states
- Check link underlines and hover states clear
- Validate focus states on all interactive elements
- Test click/touch targets sized appropriately
### Dropdowns and Selections
- Test dropdown open/close behavior
- Verify selected state displays clearly
- Check dropdown position (doesn't go off-screen)
- Test keyboard navigation in dropdowns
- Validate scroll behavior in long lists
Data and State Testing
### Empty States
- Design and review empty state layouts
- Verify messaging is clear and helpful
- Check empty state doesn't break layout
- Test CTA for actionable next steps
- Validate visual hierarchy in empty state
### Loading States
- Test all loading indicator styles
- Verify loading duration matches actual time
- Check content replacement or overlay
- Test skeleton screens vs. spinners
- Validate loading messaging
### Error and Warning States
- Test error message styling and placement
- Verify warning states are visually distinct
- Check inline vs. notification errors
- Test dismissible error handling
- Validate error recovery path
QA Checklist
### Visual QA
- [ ] Spacing consistent with design system
- [ ] Typography matches specifications
- [ ] Colors accurate to palette
- [ ] Images sharp and appropriately scaled
- [ ] Alignment perfect (grid, centering)
- [ ] No visual bugs (clipping, overflow)
### Functional QA
- [ ] All interactions work as designed
- [ ] Forms validate and submit correctly
- [ ] Links navigate to correct locations
- [ ] Buttons trigger appropriate actions
- [ ] Modals open and close properly
### Accessibility QA
- [ ] Color contrast meets WCAG AA minimum
- [ ] Keyboard navigation works end-to-end
- [ ] Screen readers describe content accurately
- [ ] Focus indicators visible throughout
- [ ] No keyboard traps
### Responsiveness QA
- [ ] Tested at 3+ breakpoints
- [ ] Touch targets minimum 44x44px
- [ ] No horizontal scroll at mobile
- [ ] Text readable without zoom
- [ ] Landscape and portrait work
### Content QA
- [ ] Copy accurate and properly spell-checked
- [ ] No orphaned words or excessive hyphenation
- [ ] Placeholder and error messages clear
- [ ] Links work and point to correct pages
- [ ] Numbers and dates formatted correctly
Documentation and Handoff
### QA Report
- Document all issues found with screenshots
- Categorize as critical, high, medium, low
- Provide reproduction steps for each issue
- Suggest fixes or improvements
- Track status until resolved
### Sign-Off Process
- Define QA acceptance criteria
- Get stakeholder approval before launch
- Document any known limitations
- Create post-launch monitoring plan
- Schedule post-launch follow-up review
Best Practices
- Create detailed QA checklist per project
- Test on real devices, not just browser emulation
- Involve actual users in usability testing
- Automate repetitive visual regression tests
- Document edge cases and workarounds
- Test early and often throughout design process
- Balance perfection with ship-ability
Common Pitfalls
- Testing only on latest devices and browsers
- Assuming mobile-responsive means accessible
- Not testing keyboard navigation thoroughly
- Skipping QA to meet deadlines
- Not involving accessibility specialists
- Testing in isolation without user feedback
- Assuming developers will catch design issues