The Figma file was approved 3 weeks ago. Since then, a validation message has been pushed down below the fold, a modal won’t close on iOS and the product grid collapses when a SKU name exceeds its width.
Those are not errors that a designer would make, but the user will say it’s bad design. To ensure what ships close to what you approved, here’s how to set up interface focused QA.
Where Good Design Breaks Down Between Handoff and Production
A design file is a drawing that depicts the best possible condition. Production must be able to handle empty states, a 60 character product name, slow networks, API errors, and a German translation which is 30% longer than the original.
Get a check-out form. In the mockup, there are six evenly-spaced fields. When the user submits, there are three errors in the browser, each error message is added to the height of the browser, and the error summary at the top scrolls out of view. The product name in the order summary fits nicely into three lines, and pushes the total below the CTA. No one made that screen.
Smaller drift piles continued to build up. Spacing tokens are hard coded, and a hover state which was not mentioned is improvised by the builder. The product no longer feels like the design file, across forty screens.
The field of QA is used to test the experience as created. Running the code is just a part of that task.
What Interface-Focused QA Actually Covers
It has 4 layers. Functional testing is a question of whether it works. Visual testing questions: does it conform to the design? Usability validation is a question of sense to an outsider to the development. Accessibility testing is a question of whether or not it is accessible to everyone.
The other three don’t say much about a green functional suite. It confirms “Save” is the request, rather than button.
The most useful UI bugs are typically technically OK but wrong: a button that is disabled but looks clickable, a spinner with no progress cue that feels like it is frozen, a destructive action that is primary. They are discovered by a tester who is using the product as a customer would.
There is a special pass for accessibility to WCAG 2.2. Navigate all flows without using a mouse, test focus order and visibility, test contrast for real states (such as disabled and error states), verify that inputs have labels, and ensure that animations do not ignore `prefers-reduced-motion`.
QA also identifies “design system drift” such as a component that is being overridden by one-off CSS or three very similar variants of a button.
Responsive Behavior, Browsers and Devices Are Where UX Quietly Fails
Responsive design is a collection of breakpoints decisions and layouts break between the breakpoints. Everything is OK at 375px and 1440px. On a tablet in portrait mode (820px), the nav wraps to two lines and blocks the hero.
Cross-browser issues persist. Some sticky and flex behaviour is different in Safari, native selects do not accept styling, `100vh` on mobile does not take into account the collapsing address bar and font fallbacks reflow pages.
Touch brings assumptions of the mouse era to light. There’s no phone equivalent to hover menus, small tap targets are accidentally tapped, and horizontal carousels are in conflict with the back swipe of the browser.
Don’t test everything. Analyze and rank browser/viewport combinations based on traffic and conversions for the past 90 days, and provide coverage for the ones with the highest revenue. Then add a purposefully one low end Android phone. So that’s where a sticky header, a cookie banner and the on-screen keyboard leave 200px of visible content and a modal with no reachable close button.
Performance Is Part of the User Experience, Not a Separate Concern
Users evaluate design, in part, based on how fast it loads. A button that jumps when it is being rendered as an ad or a tap that takes 400ms to respond is considered clunky.
Core Web Vitals added some numbers to it. LCP is the time the main content is visible, INP is how quickly the interface reacts, CLS is how much things move. They are also utilized by Google in its rankings, which means that a regression also costs in visibility.
Design decisions lead to performance debt early on: a 4MB autoplay hero video, 4 different weights of 2 custom fonts, page transitions that are full of JavaScript. A familiar scenario: the redesign passes all the stakeholders, mobile LCP drops from 1.8s to 2.9s and bounce rate rises in a week.
Define performance budgets and use Lighthouse CI for each pull request, to prevent regression from being merged. That’s not something that can be detected during a one-off audit.
Building QA Into the Design and Delivery Workflow
Begin prior to the existence of code. Prototypes should be checked by QA and they should ask themselves what each screen will look like when empty, when there is an error, when there are 500 items, and when it is in Polish. If a state is missing from Figma, it will cost one comment.
Design systems are tested for unexpected changes at the source with Storybook-style component testing and visual regression tools such as Chromatic or Percy. Change a token and you will see all of the components that it interacted with.
What should be automated: visual diffs, axe scans, performance budgets. Maintain a human nature exploratory and usability testing.
Then come to an agreement on the ownership. There must be a shared understanding of what is done in the design, development and QA process with respect to visual, accessibility and responsive requirements.
Not every team can justify a full-time QA hire, especially agencies and early-stage product teams shipping in short bursts. A St. Louis or Kansas City studio delivering a client redesign, for instance, might bring in one of the regional professional software testing firms for a pre-launch cross-device and accessibility pass, then keep visual regression checks running in-house afterward.
Conclusion
When it comes to design quality, it’s determined after handoff, in the states, devices and conditions that no one drew. Teams tested for those conditions on each release, and were close to what they approved. Teams that are using a click-through learn about gaps from support tickets.
- The LinkedIn Logo History, Colors, Font, and Meaning - 20 November 2026
- Why Quality Assurance is the Backbone of Seamless UI/UX and Web Design - 20 November 2026
- How to Design T-Shirt Art That Actually Prints Well - 19 November 2026