Web design in London
A London-registered team designing websites and product interfaces for UK businesses. Accessible and fast by design, delivered by the people who also build them, with the option to meet in person when a decision needs a room.
§ 01
London
Web Design for London
London is our home market, and it is a demanding one for design. Buyers here see good work constantly, so the bar for a credible site is high, and the audience is often sophisticated: fintech, professional services, healthcare and SaaS companies whose customers judge the interface as part of the product. The design job is rarely decoration. It is making something complicated feel obvious.
Two constraints shape UK design work more than any aesthetic trend. The first is accessibility. Under the Equality Act, a site that cannot be used by disabled people is a legal exposure as well as a quality failure, and for public sector bodies the accessibility regulations make it explicit. Accessibility is a design decision before it is a development one: contrast, focus order, target size, error handling and how you convey meaning without relying on colour are all decided in the design file. The second is performance. Core Web Vitals affect ranking, feel and trust, and most of the weight on a slow page was put there by a design choice nobody costed.
The third thing UK design has to handle honestly is consent. GDPR means cookie banners, preference controls and analytics that respect a refusal, and a banner designed as an obstacle is both a poor experience and a compliance risk, because consent obtained by dark pattern is not consent. We design those flows properly rather than dropping in a template that nudges users into agreeing. Being London-registered means UK working hours, contracts under English law, sterling invoicing and the option to run a workshop in a room when that genuinely helps.
§ 02
What is specific
Built for London
Accessibility decided in the design file
Contrast, focus order, target sizes, error states and conveying meaning without colour alone are design decisions, not development fixes. We design to WCAG from the start and test with assistive technology rather than assuming a build passes. Under the Equality Act an inaccessible site is a legal exposure as well as a quality failure, and remediation after launch always costs more than doing it once.
A performance budget, agreed early
Most of the weight on a slow page arrived through a design choice: a video hero, a heavy typeface stack, an image-led layout. We set a page-weight and Core Web Vitals budget with you before the visual direction is signed off, so the trade-off between richness and speed is made deliberately while it is still cheap. A design that cannot be built fast is not a finished design.
Consent designed honestly
Cookie banners and preference controls are part of the interface and are held to the same standard as everything else. We design them to make refusing as easy as accepting, because consent extracted by dark pattern is not valid consent under GDPR and the ICO has been clear about it. Designed properly, it is also a better first impression than a full-screen obstacle.
§ 03
Scope
What we build
Project delivery, owned end to end, for London clients.
- Design systems in Figma with real components, tokens and states, so later pages stay consistent without redesigning
- Marketing sites and product interfaces for fintech, SaaS, healthcare and professional services
- Accessible design to WCAG, including keyboard paths, focus states, error handling and screen-reader behaviour
- Design to an agreed performance budget, with Core Web Vitals treated as a design constraint
- Consent and preference interfaces designed to be honest rather than to maximise acceptance
- Front-end implementation by the same team, so the live site matches what was approved
Web Design in London: common questions
Where is Yarqat based?
Yarqat is a UK company registered in London, and it is our home market. That means UK working hours, contracts under English law, sterling invoicing and the option to meet in person when a design decision genuinely benefits from a room. We default to remote because most design work reviews well over a call and a live prototype, but here in-person is a train rather than a flight.
Do you design to accessibility standards?
Yes, to WCAG, and we treat it as a design responsibility rather than a development checklist. Contrast, focus order, target size, error handling and not relying on colour alone are decided in the design file, and we test with real assistive technology. Under the Equality Act an inaccessible site is a legal exposure, and for public sector bodies the accessibility regulations state it directly.
Do you build what you design?
Yes, and we would usually recommend it. Handing a design to a separate build team is where quality leaks, because the compromises get made by someone who was not in the design conversation, and accessibility and performance are usually the first things traded away. We implement the front end ourselves so the live site matches what you approved.
Can you work with our existing brand guidelines?
Yes. Most of our work is designing a digital system inside an existing brand rather than rebranding, which means translating print-era guidelines into components, states and tokens that work on a screen. Where a guideline conflicts with accessibility, usually contrast, we will say so and propose a compliant variant rather than quietly shipping something that fails.
How do you handle cookie consent and privacy design?
As part of the interface, designed to the same standard as everything else. Refusing must be as easy as accepting, preferences must be genuinely changeable, and analytics must respect a refusal. Consent obtained through a dark pattern is not valid under GDPR, so a compliant banner is both the lawful option and, in practice, the better first impression.
Web design in London?
A technical conversation with the engineers who would do the work. If we are not the right fit, we will say so on the call.