Web development for Britain, where the obligations end up in the code
Building for the UK changes what the code has to do. Analytics and marketing tags have to be prevented from firing before a choice is made, which is a loading-order problem rather than a banner. Accessibility has to live in the components, because public-sector supply chains contract on a standard. And hosting location becomes part of the specification rather than an afterthought.
Most of what makes a British build different is invisible on the rendered page. It shows up in which script loads when, in whether a component can be operated without a mouse, in how the site behaves on a rural connection, and in which country the database sits in. None of those are decisions you can take at the end. Each is cheap at the start and expensive to retrofit, which is the whole argument for settling them first.
The fault we are called in to fix most often looks like this. A consent banner sits on the site, and behind it the analytics snippet is hard-coded into the page template, so it runs on load whatever the visitor clicks. The banner writes a cookie recording a preference that nothing reads. Nobody notices, because the site works and the reports populate. The second version of the same failure is a component library chosen for its appearance: modals that trap nothing, custom selects a keyboard user cannot open, and colour pairs that fail against the brand's own palette. Both are found late, and both are found by somebody else.
When this work makes sense
Questions worth asking any supplier
Ask to see the network tab before consent is given rather than the banner, because the banner is the part that always looks right and the requests are the part that usually are not.
Ask which accessibility standard the components are built to and how it is tested, because 'accessible' without a named standard and a test method is a claim rather than a commitment.
Ask what the site does on a throttled connection and an older phone, because a performance budget set against a developer's laptop on office broadband describes nobody's experience.
Ask where the application, the database, the backups and the logs each live, because those are four separate answers and only the first is usually volunteered.
Ask whether a tag can be changed without a developer, because a measurement setup that needs an engineering ticket for every change is a setup that will quietly go stale.
Deliverables
Tags loaded through a consent layer that denies by default, with nothing non-essential left in the page template
A documented inventory of every script on the site, what it is for, and which consent category it belongs to
Components built against a named accessibility standard, focus management, keyboard operation, labelling and contrast tested rather than asserted
Automated accessibility checks in the build pipeline, plus manual keyboard and screen reader passes on the flows that earn money
Performance budgets set on a mid-range device and a constrained connection rather than on office broadband
Hosting, database, backup and log locations documented, so you can answer the question when a customer's procurement team asks it
A written handover of the consent configuration, so a future marketing hire cannot undo it by pasting a script into a template
Built with
Process
We start a UK build with a script inventory, even on a project that is replacing the site entirely. Listing what currently loads, what it belongs to and who asked for it usually produces two findings: several tags nobody can account for, and at least one that fires before any consent decision. That list becomes the specification for the consent layer, and it is far easier to write while the old site is still up. The accessibility standard is agreed in the same week, because it governs component choices and there is no cheap way to change it afterwards.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Three ways to stop tags firing before consent
Consent mode in the tag manager
Fits: Sites with a manageable number of tags, where marketing needs to keep control of them
Limits: It governs tags that go through the manager and nothing else, anything hard-coded into the template ignores it entirely
Server-side tagging behind the consent signal
Fits: Larger sites where third-party scripts are both numerous and a performance problem in themselves
Limits: More infrastructure to run and pay for, and it needs somebody who will maintain it after launch
Blocking at the template, tags injected only after a choice
Fits: Smaller sites, or any site where the guarantee should be structural rather than configured
Limits: Every new tag needs a developer, which is safe and slow, and marketing teams find it frustrating
Case studies
No published UK web development case study yet. Our London office is on the 37th Floor, 1 Canada Square, Canary Wharf, London E14 5AA, and UK enquiries go to uk@mbgdesk.com. We will publish client work once we have permission to name the business and results that can be evidenced rather than described.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Our cookie banner is installed. Is that enough?
Often not, and it is quick to check. Open the site in a clean browser, refuse everything, and look at what the browser actually requested. If analytics, advertising or session-recording endpoints appear, the banner is recording a preference nothing enforces. That is a build fault rather than a banner fault. Whether it is also a legal problem is a question for your data protection adviser, not for us.
Which accessibility standard should we build to?
Whichever one your contracts name. Public-sector buyers in the UK generally hold suppliers to WCAG at a stated level, and enterprise procurement increasingly asks the same question. If nothing names a standard, pick one anyway and test against it, because 'accessible' with nothing behind it cannot be evidenced at the moment somebody asks you to evidence it.
Can accessibility not simply be audited at the end?
It can. What you get is a list of faults distributed across every component, which is the most expensive shape a remediation can take. Building the standard into the component library means each pattern is solved once and reused everywhere. The end-of-project audit still happens. It becomes a check rather than a discovery, which is a much better week for everyone.
Our customers are all in the UK. Does hosting location matter?
It matters for two different reasons that get conflated. One is latency, where a nearby region measurably helps. The other is being able to say where personal data sits, which comes up in procurement questionnaires and in your own records of processing. We document the application, database, backup and log locations separately, because they are frequently not the same place.
How slow is 'not on fibre' in practice?
Slower than most teams design for, and unevenly distributed, rural areas, older housing stock, and mobile coverage on the roads between them. The practical response is to test on a throttled connection and a mid-range phone rather than guess, and to set a budget the build is held to. Sites that fail here usually fail on third-party scripts rather than on their own code.
Will consent-gated analytics wreck our reporting?
It changes it. You will see fewer sessions, because you are only counting the ones you are permitted to count, and modelling fills some of the gap. What matters more is that the baseline moves once, at the point the gating is fixed. Comparisons across that date are meaningless and should be labelled as such rather than explained away a year later.
We have a site already. Can you fix it rather than rebuild?
Usually, and the script inventory tells us which. Consent gating can almost always be retrofitted. Accessibility depends on the component library: a design system with sound focus handling and honest markup can be brought up to standard, while a theme built on nested divs and bespoke widgets is often cheaper to replace than repair. We will tell you which one you have before you commit.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.