Accessibility is a design constraint here, not a report you receive afterwards
What changes in Britain is when accessibility enters the process. Here it belongs to design: contrast pairings, visible focus, target size and motion decided while the palette and the type scale are still being chosen, rather than audited afterwards. The consent banner is part of that same visual system, and it is usually designed by nobody.
Most British websites are designed first and checked for accessibility afterwards. The check produces a list, the list goes to a developer, and the fixes are applied to a visual system that was never built to hold them. Contrast gets nudged, focus rings get bolted on, and the result satisfies a tester while looking as though two different people made it. Designing inside the constraints from the first palette avoids all of that.
A remediation pass is where design decisions go to be overruled. The brand grey that reads beautifully in a deck fails against white, so somebody darkens it on the buttons but not the body text, and the site now has two greys. The designer removed focus outlines because they interrupted the look, so a developer restores the browser default, which matches nothing on the page. Tap targets were sized for a mouse, so spacing is opened up at the mobile breakpoint only and the rhythm breaks. None of these are hard problems at the start. All are expensive once a system has been built around the wrong decision.
When this work makes sense
Questions worth asking any supplier
Ask to see the palette with its contrast pairings already worked out, because an untested palette is one that gets changed after the build.
Ask how focus states are designed rather than whether they exist, because a default browser outline on a custom component is an unpainted patch.
Ask what happens when a visitor has reduced motion switched on, because animation with a single setting is either stripped out or left running over people it makes unwell.
Ask who designs the consent banner, because if the answer is the legal adviser or the plugin vendor, the first thing every visitor sees was designed by nobody.
Ask whether accessibility is priced as a separate line, because if it is, it is a pass added at the end rather than a constraint the design was built inside.
Deliverables
A colour system with contrast pairings resolved at the palette stage, so nothing fails once it reaches a browser
Designed focus states for every interactive element, drawn as part of the component rather than inherited
A type scale and spacing rhythm that holds together when a visitor enlarges text
Target sizes and spacing set once for touch and pointer, not patched into the mobile breakpoint
Motion specified with a reduced-motion alternative, so the design still communicates when animation is off
A designed consent banner, detail layer included, that belongs to the visual system rather than covering it
Documentation recording the constraint behind each decision, so the next person does not quietly undo it
Built with
Process
We settle the palette and the focus treatment before any page is laid out. That ordering is deliberate, because these two decisions constrain everything downstream and they are the two most commonly left until last. We take the brand colours as given and work out which pairings can carry body text, which can carry large text only, and which are decorative, then design the focus treatment as a deliberate part of the visual language. Once those are fixed, layout is comparatively free. Reversed, the layout dictates the colour and the compromises begin.
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 arrive at an accessible design
Design it in from the palette onward
Fits: Redesigns and new builds, where the constraint shapes the system rather than fighting it
Limits: Needs the brand owner involved early, and some brand colours turn out to be decorative only
Build first, audit, then remediate
Fits: Sites already built, where the design cannot be reopened and a defensible position is needed
Limits: Produces a compliant site that looks patched, and the issues return whenever someone adds a component
Buy an accessible theme
Fits: Small sites with little custom interaction and no in-house design capability
Limits: The template is accessible until customised, and the first brand colour applied usually breaks the text
Case studies
Nothing is published yet. There is no UK web design case study, because no client work has been released. Our London office is at 37th Floor, 1 Canada Square, Canary Wharf, London E14 5AA, and enquiries reach us at uk@mbgdesk.com. We will publish once we have permission to name the organisation.
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
Can we keep our brand colours?
Usually most of them, in some role. The work is deciding which pairings carry body text, which carry large text only, and which are decorative. A grey that fails against white may be perfectly usable as a panel behind white text.
Is accessibility a legal requirement for us?
That depends on what your organisation is and who it serves, and the judgement rests with your own legal adviser. What we can say is that public sector suppliers are held to a published standard, and the same expectations now appear routinely in private procurement.
Why design focus states when the browser has one?
Because the browser outline was drawn for a default button on a white page, and your components are neither. On a dark panel it disappears, on a rounded card it cuts the corners, and on a custom control it may not appear at all.
What does reduced motion change in a design?
Every transition needs a second version that conveys the same thing without movement. A panel that slides in to show where it came from has to say that another way. If the only version is animated, switching motion off removes information rather than decoration.
Who should design the cookie banner?
A designer, working to wording your legal adviser is content with. On most British sites it is the first thing a visitor sees and the last thing anyone designs. The wording is a legal question; the hierarchy, contrast and how much it covers are design ones.
Will designing this way look plain?
No, though it rules out light grey on white, untreated text over a busy photograph, and interaction that signals state by colour alone. Those are constraints in the way a print designer accepts that ink soaks into uncoated stock, and they tend to clarify a system.
Do you build what you design?
We can, and the implementation questions, accessible component behaviour, consent-gated analytics, hosting and performance, sit on our UK web development page. Plenty of clients take the design system to an in-house team instead, which works when the documentation records why, not only what.
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.