UI Polish Checklist: 24 Details No Design File Specifies
Last updated: November 18, 2026
UI polish is the finishing pass on an interface: the details a design file rarely specifies, such as focus rings, hit areas larger than the visual, loading-state timing, tabular numbers, and how long text breaks. Design QA asks whether the build matches the design. Polish asks whether it feels finished in the states nobody drew.
This checklist is for the designer and the developer reviewing a build together. It assumes the page already matches its design file. If you have not checked that yet, start with the design QA checklist. The 24 checks below cover what is left: spacing details, type and numbers, color, interaction states, targets and motion, and loading and edge-case states. Each one names the standard or guideline it comes from, so a disagreement can be settled with a source instead of taste.
Why UI Polish Matters
People judge an interface before they use it. In a 2006 study by Lindgaard and colleagues, participants rated web pages for visual appeal after seeing each one for 50 milliseconds, and those ratings closely matched the ones they gave after 500 milliseconds. Appeal feeds trust too: in a Stanford study of 2,684 people judging websites, the design look came up in 46.1% of their comments about credibility, more than any other feature.
Polish also covers speed you can feel. Jakob Nielsen’s response-time limits put the feeling of an instant response at about 0.1 second. Past that, people notice they are waiting. Each check below is small, but people meet them on every click, and together they decide whether a product feels finished.
UI Polish vs Design QA
| Design QA | UI polish | |
|---|---|---|
| Question | Does the build match the design? | Does it feel finished, including the states nobody drew? |
| Reference | The design file and its specs | WCAG, platform guidelines, and how the page behaves in use |
| Typical findings | Wrong color, padding off by 4px, a missing section | No focus ring, a 16px close button, a spinner that flickers, a name that overflows |
| When | As each screen is built | Once screens match, before release |
The two overlap at the edges. A missing hover state is a design QA finding when the file shows one, and a polish finding when nobody drew it.
Spacing and Alignment
- 1. Optical alignment: Align icons and text by what the eye sees, not by their boxes. A play icon, an arrow, or a glyph with uneven built-in padding can look off-center while measuring as centered. Vercel’s interface rules allow a 1px adjustment when perception and geometry disagree. Check icon buttons and icon-plus-label pairs at 200% zoom.
- 2. Concentric corners: When a rounded element sits inside another, the inner radius should be smaller so both curves share a center. Inner radius equals outer radius minus the padding between them, so a card with a 16px radius and 8px of padding holds a button with an 8px radius. Vercel’s Web Interface Guidelines call these nested radii.
- 3. No dead zones: A checkbox and its label should be one click target, which Vercel’s rules require. In a list, put the space between rows inside each row as padding instead of as a gap, so a click between two rows still lands on one.
- 4. Every gap comes from one scale: Gaps of 14px, 15px, and 18px on the same screen read as unfinished even when nobody can say why. Pick a scale, such as 4px steps, and use its tokens. Drift is the norm: our audit of 276 agency homepages found the median site used its own design tokens for 24% of its styling values, and across 375 product-company homepages the scans found an average of 47 hard-coded values per site.
Type and Numbers
- 5. Tabular numbers where digits change or line up: With proportional figures, digits have different widths, so a timer shifts sideways as it ticks and a column of prices will not line up. Set
font-variant-numeric: tabular-numson prices, tables, timers, and counters. MDN lists it as available across browsers since January 2020. - 6. Long text has a plan: Test the longest real name, email address, title, and translated string. Each text container should truncate with an ellipsis, clamp to a set number of lines, or wrap, on purpose. In a flex layout the child needs
min-width: 0before truncation works, one of the fixes in Vercel’s interface checks. - 7. Typographic details: Use the ellipsis character (…) instead of three periods, curly quotes instead of straight ones, and end labels that open more input or show progress with an ellipsis, such as “Rename…” or “Saving…”. All three are in Vercel’s guidelines.
- 8. Inputs are at least 16px on phones: iOS Safari zooms in when someone focuses an input whose text is smaller than 16px. Vercel’s guidelines keep mobile input text at 16px or larger, and never disable browser zoom to hide the problem.
Color and Contrast
- 9. Text meets 4.5:1: WCAG 2.2 success criterion 1.4.3 asks for a contrast ratio of at least 4.5:1 between text and its background, and 3:1 for large text. The thresholds are not rounded, so 4.499:1 fails. Placeholder text, captions, and secondary metadata are where light grays slip under.
- 10. Borders, icons, and focus rings meet 3:1: Success criterion 1.4.11 applies a 3:1 minimum to the visual parts that identify a control and its state, such as an input border, a checkbox outline, or an icon-only button, measured against the colors next to them.
- 11. Interaction raises contrast: Hover, pressed, and focus states should be more visible than the resting state, not less, as Vercel’s guidelines put it. A hover style that lightens a button can drop its label below 4.5:1.
- 12. Color is never the only signal: An error field, a status dot, or a required marker needs text or an icon as well as color, under success criterion 1.4.1. Check the page with the vision deficiency emulation in Chrome DevTools’ Rendering tab.
Interaction States
- 13. Every focusable element shows focus: Keyboard users need to see where they are. Use
:focus-visibleso the ring appears for keyboard focus without showing on every mouse click, and never removeoutlinewithout a visible replacement, as Vercel’s rules require. Press Tab through the whole page once. - 14. Focus never hides behind sticky bars: WCAG 2.2 success criterion 2.4.11 fails a focused element that is entirely hidden by content the author added, such as a sticky header, a cookie banner, or a chat button. WCAG technique C43 fixes it with
scroll-paddingon the scroll container, sized to the sticky bar. - 15. Hover styles only on devices that hover: On a touch screen, a tap can trigger a hover style meant for a mouse. Wrap hover styles in
@media (hover: hover), as Rauno Freiberg’s list of interface details recommends. - 16. Every custom control has a pressed state: Apple’s Human Interface Guidelines warn that without a press state, a button “can feel unresponsive”. Keep it subtle: Freiberg suggests scaling a pressed button to about 0.96, not 0.8. Every state a button needs, with its CSS, is in our guide to button states.
Targets and Motion
- 17. Hit areas are at least 24 by 24: WCAG 2.2 success criterion 2.5.8 sets a minimum target of 24 by 24 CSS pixels, with exceptions for spaced-out targets and links inside a sentence. Platform guidance goes further: Apple asks for a hit region of at least 44 by 44 points, and Material Design suggests 48 by 48dp touch targets. A 16px icon button can keep its look and grow its target with padding or an invisible pseudo-element.
- 18. Feedback within 100 milliseconds: Nielsen’s limit for an interaction to feel instant is about 0.1 second. When the real work takes longer, respond right away anyway: show the pressed state, highlight the clicked item, or update the UI optimistically and roll back if the server refuses, the pattern Vercel’s guidelines describe.
- 19. Short motion on the right properties: Freiberg’s list keeps interaction animations under 200 milliseconds so they feel immediate. Animate
transformandopacity, which browsers can composite cheaply, and name the properties in a transition instead of writingtransition: all, as Vercel’s rules require. - 20. Reduced motion is respected: Some people set their device to reduce motion because animation can trigger discomfort, including for people with vestibular motion disorders (MDN). Use
@media (prefers-reduced-motion: reduce)to remove or soften non-essential movement, and test it with the emulation in Chrome DevTools’ Rendering tab.
Loading, Empty, and Edge-Case States
- 21. Loading states that do not flicker: On a fast response, a spinner that appears and vanishes reads as flicker. Vercel’s guidelines suggest waiting about 150 to 300ms before showing one and keeping it visible for at least 300 to 500ms. Skeletons should match the final layout so nothing jumps when content arrives.
- 22. Every state is designed: Check each screen empty, with one item, with hundreds, and with an error, and make sure every version offers a next step. Vercel’s guidelines list empty, sparse, dense, and error states next to a rule against dead ends.
- 23. Images reserve their space: Give images an explicit
widthandheight, or anaspect-ratio, so the layout does not shift as they load (Vercel’s checks). Without it, text moves after the page appears, sometimes under a cursor about to click. - 24. The page reflows at 320 pixels: Success criterion 1.4.10 asks that content work at a width of 320 CSS pixels without scrolling in two directions, which is what a 1280px window looks like at 400% zoom. Check for sideways scrollbars at 320, 768, and 1440px, and on a wide monitor.
Who Owns Each Check
Most polish work is shared, which is why it slips: each side assumes the other has it. Agree who owns each area before the review, not during it.
| Area | The designer decides | The developer checks in the build |
|---|---|---|
| Spacing and alignment | The spacing scale, nested radii, optical adjustments | Values come from tokens, with no stray pixel values |
| Type and numbers | The type scale, truncation rules, tabular figures | min-width: 0 in flex rows, 16px inputs, real long strings |
| Color and contrast | State colors that pass 4.5:1 and 3:1 | Contrast in the real build, including hover |
| Interaction states | Hover, pressed, focus, disabled, and loading styles | :focus-visible, no hover on touch, focus never hidden |
| Targets and motion | Target sizes, durations, reduced-motion versions | Hit areas in code, transform and opacity only |
| Loading and edge cases | Empty, sparse, dense, and error screens | Every state reachable, images sized, 320px reflow |
How to Run a UI Polish Pass
- Wait for design QA to finish: Polish a screen once it matches its design. Polishing a layout that is about to change is work you do twice.
- Go through with the keyboard only: Tab from the top of the page to the bottom. Every stop should be visible, in a sensible order, and never under a sticky bar (checks 13 and 14).
- Change the conditions: In Chrome DevTools, throttle the network to see loading states, emulate reduced motion and vision deficiencies in the Rendering tab, and resize to 320, 768, and 1440px.
- Feed it real edge cases: Paste the longest name you can find, empty every list, and make a request fail on purpose. Checks 6, 21, and 22 can only be tested this way.
- File each finding with its values: Write down the element, the state, the expected value, and the value in the build, with a screenshot of that state. “No focus ring on the search field” with a screenshot is a fix a developer can make in one pass. “Make it feel smoother” needs a conversation first. More on that in how to report UI bugs.
Where Tools Help and Where They Do Not
Automated checks are good at the measurable half of this list. Contrast ratios, target sizes, and hard-coded values can be measured on every page. Timing, motion, and whether a state feels right still need a person going through the page.
OverlayQA covers the measurable half from the browser. An element capture saves the element’s selector and computed CSS with the screenshot, and Spacing in the capture toolbar shows an element’s padding and the gaps to the nearest visible elements as you hover. Auto Review scans a page for design inconsistencies, missing interactive states, form problems, responsive gaps, dead UI, and leftover placeholder content, and the Accessibility Audit catches contrast, touch-target, and ARIA issues. Findings can be turned into issues and exported to your tracker.
Frequently Asked Questions
What is UI polish?
UI polish is the finishing pass on an interface: the details a design file rarely specifies, such as focus rings, hit areas, loading-state timing, tabular numbers, and long-text handling. It comes after the build matches the design.
What does UI polish include?
Six areas: spacing and alignment, type and numbers, color and contrast, interaction states, targets and motion, and loading, empty, and edge-case states. Each has measurable standards in WCAG 2.2 and the major platform guidelines.
What is a UI polish pass?
A polish pass is a review of a finished screen against a checklist like this one, done with the keyboard, a slow network, reduced motion, long text, and several screen widths. Each finding is filed with the element, the state, and the expected value.
Is UI polish the same as pixel-perfect design?
No. Pixel-perfect work checks the build against the design file. Polish covers what the file does not show, such as focus, pressed, loading, and empty states, so a pixel-perfect page can still feel unfinished.
Who is responsible for UI polish, designers or developers?
Both. Designers decide the values and the states. Developers make sure the build keeps them under real data, devices, and input methods. Agreeing who owns each area before the review keeps any of it from slipping.
When should you do a UI polish pass?
After a screen matches its design and before release. Start with shared components, because a fix to a button or an input fixes every page that uses it.
Can automated tools do UI polish?
Partly. Tools can measure contrast, target sizes, hard-coded values, and missing interactive states on every page. Motion timing, how loading feels, and keyboard order still need a person to go through the page.
Detect missing interactive states, contrast and touch-target problems, and hard-coded values with AI analysis, CSS extraction, and accessibility auditing. Export each issue to Jira, Linear, and more.