Frequently asked questions

For public sector bodies, yes: the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 require WCAG 2.2 AA and a published accessibility statement. For private businesses, the duty comes from the Equality Act 2010, which requires reasonable adjustments for disabled people. It names no technical standard, but WCAG 2.2 AA is the accepted way of demonstrating you have made them.

No. Overlay products that promise instant compliance through a single script do not deliver it. They are widely opposed by disabled users, and their presence has featured in legal claims rather than preventing them. Accessibility is a property of the underlying HTML — how headings are structured, whether controls are reachable by keyboard, whether text has sufficient contrast. A script layered on top cannot retrofit that.

Only if it sets non-essential cookies. If you run no analytics cookies, no advertising pixels and no third-party embeds, you do not need a consent banner at all — though you still need a privacy notice. For most small businesses, removing the trackers is simpler and cheaper than managing consent for them, and it means no banner standing between a visitor and your content.

Most UK organisations that process personal data must pay the ICO data protection fee, which starts at £52 a year for small organisations. Running a contact form is processing personal data. There are exemptions, so check your position using the ICO’s own self-assessment tool rather than assuming either way. If you are registered, your registration number belongs in your privacy notice.

Genuine ranges in 2026 run from roughly £500 for a template-based brochure site to £15,000 or more for a custom build with bespoke functionality. Most small business sites that need to actually perform sit between those extremes. Point28 publishes real starting prices rather than “contact us”, because a price you cannot see cannot be compared. Anything quoted without a written scope should be treated with suspicion — the number moves once work starts.

Design, build, WCAG 2.2 AA accessibility conformance, on-page SEO, structured data, a working contact form, and written handover documentation. Hosting is on a static CDN and normally costs nothing. The separately priced accessibility and SEO services on the pricing page are retrofits for sites we did not build — a Point28 build already includes both, so you are never buying the same thing twice. What is not included is content writing beyond light editing, photography, and any third-party licence or subscription your site needs — those are quoted separately so you can see them.

Not by default. A static site has no licence, no plugin subscriptions and no mandatory maintenance retainer. You will pay for your own domain, typically £10 to £20 a year. Optional extras — a content editor, ongoing SEO work, or an automation that calls a paid API — carry their own running costs, and those are stated before you commit.

No. A build is a one-off project with a fixed price and a written scope — when it is delivered and paid for, the relationship has no remaining term. Nothing renews automatically, there is no rolling agreement, no notice period, and no cancellation process, because there is nothing running to cancel. Businesses are not consumers in UK law, so a signed business contract has no cooling-off period — which is exactly why the terms here are short enough to read before you sign, and why the price and scope are on paper before any money moves.

SEO competes for a position in a ranked list of links. GEO — generative engine optimisation — competes to be the passage an AI answer engine lifts into a generated answer and attributes. They share technical foundations, but reward different writing: answer engines favour self-contained paragraphs, explicit definitions and concrete figures over keyword placement and internal link equity.

No, and any agency that does is describing something it cannot control. Nobody owns Google’s index or a language model’s output. What can be guaranteed is the work itself: the technical baseline, the structured data, the content structure, and a dated set of measurements you can reproduce independently. Progress is reported against that baseline rather than against a promise.

Ten to fifteen working days for a standard five-to-eight page site, measured from the point where content and brand assets are in hand. The build is rarely the bottleneck. What usually extends a project is waiting on copy, photography or a decision, so the schedule is agreed up front with those dependencies named.

Yes, outright. The site is handed over as a git repository you control, along with the domain and all content. There is no proprietary builder to remain locked into and no licence that expires. If you later want to move to another developer, everything they need is already in your possession.

Yes. Every project ships with written handover documentation naming where each piece of text and every image lives. For sites that need frequent updates a content editor is wired in so routine changes need no developer. For sites that change twice a year, that layer is usually not worth its complexity — and we will say so rather than sell it.

Nothing. That is the design. Your domain, hosting and analytics accounts are registered to you — not to us — so the site keeps running whether or not this studio exists. The code is a git repository in your possession with written handover documentation, so any competent developer can pick it up without ever speaking to us. A small studio owes you this answer in advance: businesses whose designer vanished, taking the credentials with them, are one of the most common rescue jobs in this industry. You cannot be one of them, because we never hold anything of yours to begin with.