What we do
Tools
Industries
Department
How we workLet's talk →
Home/Frontend Developer
Frontend Development

Hiring a Frontend Developer: What the Design File Leaves Out

A design shows how each screen looks on a good day. A frontend developer also has to decide what happens while it loads, when a search finds nothing, when a name is twice as long as the mockup's, on a slow phone, and for someone using a keyboard or a screen reader. Those are the parts that separate a build that matches the pictures from one people can actually use.

From design file to a screen people can use

Whoever builds it, these are the steps where frontend projects either hold together or start drifting from the design.

  1. 1

    List the states the mockup skipped

    For each screen: loading, empty, error, too much data, and what a logged-out visitor sees. Agree them with the designer before building, or the developer invents them under deadline.

    Watch for: the error message on a failed payment. It's the state customers remember.

  2. 2

    Build components, not pages

    Buttons, form fields, cards and tables built once and reused, with the colors and spacing taken from the design's own styles. When the design changes mid-build, one component changes instead of forty screens.

  3. 3

    Use the right HTML underneath

    A button that's a real button, fields with labels, headings in order. It costs nothing extra at build time, and it's most of what makes a page work with a keyboard, a screen reader and search engines.

  4. 4

    Measure speed on an ordinary phone

    Google's Core Web Vitals give the targets: the main content visible within 2.5 seconds (LCP), a response to taps within 200 milliseconds (INP), and a layout that doesn't jump around while loading (CLS under 0.1).

    Watch for: large hero images and third-party scripts such as chat widgets and trackers. They're the usual reasons a page misses those numbers.

  5. 5

    Check it against WCAG

    The Web Content Accessibility Guidelines, now at version 2.2, are the standard most accessibility requirements point to. Level AA includes a 4.5:1 contrast ratio for normal text, visible keyboard focus and text that still works when zoomed.

  6. 6

    Agree the data contract with the backend

    What each screen asks the backend for and what comes back, written down. Most "the frontend is broken" bugs turn out to be the two sides expecting different shapes of data.

Six tests you can run on the finished screens yourself

No technical knowledge needed. Try them on your own site, or on a build you've been asked to approve.

  • Put the mouse away and press Tab

    You should be able to reach every link, field and button in a sensible order, see where you are at each step, and finish the main task, such as a checkout or a booking.

  • Zoom the browser to 200%

    Text should get bigger without overlapping, getting cut off or forcing you to scroll sideways to read a line.

  • Run the page through PageSpeed Insights

    Google's free tool reports the Core Web Vitals, from real visitors where there's enough traffic. Check the mobile result, not just desktop.

  • Turn on a screen reader for one task

    VoiceOver on a Mac or iPhone, or NVDA on Windows. Unlabelled buttons announced as just "button" mean some customers can't tell what they do.

  • Type a very long name and a very long address

    Real customer data is messier than the mockup's. Layouts that break here will break for someone every day.

  • Use it on the oldest phone your customers carry

    Developers test on fast machines. A mid-range phone on a weak connection is closer to what many of your visitors have.

Questions people ask

Do you specialize in one framework or work across React, Vue, and Angular?

We work across React, Vue and Angular, and plain JavaScript when a page doesn't need a framework. If you already have a codebase, we stay in its framework. For a new build, the choice follows what the screens need to do and who will maintain them.

What if the design keeps changing mid-build?

It usually does, and the component approach above is how we absorb it: a change to a button or a card style is made once. Larger changes, such as a new screen or a different flow, get priced as they come, so the cost stays visible as it moves.

Is frontend work cheaper than full-stack?

It's a smaller scope, so often yes. But screens need data, and if there's no backend yet, or it's a tangle, the frontend can't be finished without it. A full stack quote covers both sides when that's the real job.

Do we have to make our website accessible?

It depends on where you sell and what you sell. The European Accessibility Act has applied to many online services sold to EU consumers since June 2025, and US businesses face lawsuits over inaccessible sites. WCAG 2.2 AA is the usual target either way, and it also makes the site easier for everyone to use.

What should a new frontend developer learn first?

HTML and CSS properly, then JavaScript, then one framework. Learn accessibility and performance measurement alongside them, not afterwards. A portfolio piece that passes the six tests above stands out, because most don't.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.