Reference
Design QA Glossary
Plain definitions of the accessibility, design QA and bug reporting terms your team runs into, and the OverlayQA workflow that detects each problem.
Accessibility
Found by Accessibility Audit
- Color contrast ratio: How much lighter text is than its background. WCAG AA asks for 4.5:1 on normal text.
- Alt text (coming soon): The text a screen reader reads in place of an image, and what most browsers show if the image fails to load.
- ARIA label (coming soon): An attribute that gives a control an accessible name when its visible text is missing or unclear.
- WCAG: The W3C's accessibility guidelines, tested at three levels: A, AA and AAA.
Design QA
Found by Visual Comparison, Design System Audit, Auto Review
- Design QA: Checking a built page against the approved design before it ships.
- Design tokens: Named variables that store one design decision, like a color or a spacing value.
- Design system drift: When shipped CSS slowly stops matching the values your design system defines.
- Interactive states (coming soon): How a control looks on hover, focus, press and disable, and what breaks when one is missing.
Bug reporting
Captured with Visual Bug Capture, tracked with Issue Tracking
- UI bug: A defect in what a person sees or touches: layout, spacing, color, text or a control.
- Steps to reproduce (coming soon): The exact actions that make a bug appear again, written so a developer sees it on the first try.
- Severity vs. priority (coming soon): Severity is how bad a bug is. Priority is how soon the team fixes it.
- Regression testing: Re-checking what already worked after a change, so fixed bugs stay fixed.
- User acceptance testing: The final check where the client or business confirms the build does what they asked.
Last updated October 2026