Interface design that holds up at 200% zoom and on a bad screen
An interface is judged in conditions the design file never simulates: a cheap monitor in a bright room, browser zoom at 200 per cent, a user navigating entirely by keyboard, and content twice as long as the placeholder. We design for those conditions from the start. Type scales that stay legible, contrast that clears WCAG 2.1 AA, focus states that are visible without hunting, and layouts that behave when the text does not cooperate.
You probably need this if
- The brand grey fails contrast
- Focus states were removed for looks
- Status is communicated by colour alone
- Touch targets are too small and too close
Where these projects go wrong
Four failure modes we see repeatedly. Knowing them up front is most of the battle.
- 01
The brand grey fails contrast
Light grey body text at 3:1 looks refined on a designer's calibrated screen and is unreadable on a laptop in daylight. AA requires 4.5:1 for body text, and this is the single most common failure we find.
- 02
Focus states were removed for looks
The default outline was turned off and nothing replaced it. Anyone navigating by keyboard now has no idea where they are, and that includes power users, not only assistive-technology users.
- 03
Status is communicated by colour alone
Red and green dots with no label, icon or shape difference. Around one in twelve men cannot reliably distinguish them, and the information is simply unavailable to them.
- 04
Touch targets are too small and too close
A row of 28-pixel icon buttons with no spacing. On a phone, held one-handed, the delete button sits four pixels from the one people meant to press.
- Type scale, spacing scale and grid definition
- Colour palette with verified contrast ratios
- Component states including hover, focus and disabled
- Responsive layouts across defined breakpoints
- Icon set and illustration direction
- Form design with inline validation patterns
- Dark mode variants where required
- Design tokens exported for implementation
The engagement, step by step
- 01
Set the foundations before the screens
Type scale, spacing scale, colour ramp and radii decided first, as tokens. Screens designed before the foundations exist produce twenty-eight one-off spacing values.
- 02
Verify contrast while choosing colours
Every text and interface colour checked against its background as it is picked. Discovering a palette fails AA after fifty screens are designed means redoing the palette and the screens.
- 03
Design the states, including focus
Default, hover, focus-visible, active, disabled, loading and error for every interactive component. Focus indicators need at least 3:1 contrast against what surrounds them.
- 04
Stress the layout with real content
Longest realistic name, empty list, a hundred rows, translated strings if relevant, and 200 per cent zoom. Layouts that only work with placeholder text do not work.
Benefits & business outcomes
What changes when this work is done properly — not activity metrics, business results.
- 01
Interfaces that survive real content
Layouts that hold long names, translations and dense tables — placeholder-perfect screens that break in production are rejected.
- 02
Contrast and focus you can ship
WCAG 2.1 AA contrast, visible focus states and keyboard paths designed in — accessibility is not a later polish pass.
- 03
Consistent styling without a full system yet
Type scale, colour and component states aligned so the product stops looking like five different hands.
- 04
Dense SaaS UI that stays scannable
Hierarchy and spacing for control-heavy screens — the usual failure mode of 'just make it pretty' briefings.
The stack for this work
- Figma
- Design tokens
- Tailwind CSS
- Storybook
- Radix UI
- Stark
- Axe DevTools
- Style Dictionary
- Products that work well and look unfinished
- Teams shipping with inconsistent, ad-hoc styling
- Companies with an accessibility obligation to meet
- SaaS interfaces dense with data and controls
Working remotely with teams in United States, United Kingdom, Canada, Europe, United Arab Emirates, Saudi Arabia, Singapore, Australia, New Zealand and India.
Industries we serve
The same engineering patterns apply across sectors — the domain language and constraints change.
- SaaS dashboards
- Fintech & trading UIs
- Healthcare clinical tools
- E-commerce admin
- Productivity & collab apps
- Automotive & IoT consoles
- Public-facing portals
Why choose BuildsInfinity
Practical reasons teams choose BuildsInfinity for ui design services — grounded in how we actually work, not a slogan list.
- 01
Designed for cheap monitors and zoom
UI design services that only look right on a designer's display fail users. We check the conditions people actually use.
- 02
States are first-class
Hover, disabled, error and empty are in the file. Engineering should not invent the greyed-out button.
- 03
Works toward a design system when needed
If inconsistency is organisational, we say when tokens and components are the next step — and when a focused UI pass is enough.
Related services
Product Design Services
Problem to buildable interface — flows, prototypes, every screen state, and a handover specification with tokens and behaviour defined.
UX Research Services
Interviews, usability testing and analytics review, synthesised into prioritised findings a team can act on this month.
Design System Development
Tokens, an accessible component library, Storybook documentation and the rules that keep it from fragmenting.
Need ui design services?
Send a paragraph about the problem and you will get a considered reply from an engineer — a shape, a rough timeline and an honest view on whether we are the right fit. Request a consultation or project estimate anytime.