$(cat <<"HTML"
When people ask for a web design quote in 2026, the old questions still matter: how many pages, what does it need to do, and who is going to update it? But the first conversation now has two sharper questions sitting at the front of the table: can people use it easily, and will it load fast enough to feel trustworthy?
That is not a trend piece. It is a quoting reality.
Accessibility and performance affect the shape of the work from day one. If a site needs keyboard-friendly navigation, readable contrast, proper form labels, faster mobile delivery, or accessible PDFs, the scope changes. If the homepage is loaded with oversized images, video backgrounds, and third-party scripts, the performance budget changes too. A quote that ignores those decisions is not cheaper; it is just unfinished in a more expensive font.
For official guidance, W3C’s WCAG 2.2 overview explains newer success criteria such as target size, accessible authentication, and consistent help. Google’s Core Web Vitals guidance keeps the focus on real-user experience signals like loading speed and layout stability. Those are not side quests. They are part of the job.
Why accessibility and speed belong in the first conversation
Good designers have always cared about usability. The difference now is that clients are more aware of what they need to ask for, and browsers, search engines, and users are less forgiving when basics are missing. A site that looks polished but fails on mobile keyboard use or takes too long to settle on screen can undermine the work before a visitor reads a single line.
Three examples come up again and again:
- A charity PDF that cannot be read properly by a screen reader, so supporters cannot access the information they were sent.
- A booking form where labels are unclear, error messages are vague, and the submit button is too small to tap comfortably on mobile.
- An artist portfolio where high-resolution images look beautiful but the page shifts around while they load, making the layout feel broken.
That is why clients should raise accessibility and speed before the quote lands. If you wait until the build is nearly done, you are asking for redesign work, not just implementation.
What to tell a designer before asking for a quote
A useful quote starts with useful inputs. If you want a comparable estimate, give the designer the shape of the website, not just the wish for one.
Tell them the site’s main job
- Sell products online
- Generate enquiries
- Support appointments or bookings
- Publish information and updates
- Raise donations or membership signups
- Showcase artwork, services, or case studies
Tell them what content you already have
- Text drafted or still to be written
- Photos, logos, brand files, and video
- Downloads such as brochures, policies, reports, or forms
- Existing pages that must be migrated or replaced
Tell them what the site must do
- Contact form
- Donation form
- Booking system
- Newsletter signup
- Shopping cart
- Multilingual content
If you need background pages about the team or service approach, point to the relevant sections on the About page, the website design services page, and the main home page so the brief sits in the same universe as the rest of the site.
The practical checklist
Before you contact a designer, make a short checklist. It keeps the first call focused and stops quotes from drifting into vague theater.
| Topic | What to decide | Why it affects the quote |
|---|---|---|
| Accessibility | Any known needs for keyboard use, contrast, captions, transcripts, or readable PDFs | Changes the design and content rules from the start |
| Mobile layout | How the site should work on phones and tablets | Mobile-first layout choices shape templates and content order |
| Core Web Vitals | Whether load speed, interactivity, and layout stability are priorities | Influences image handling, script use, and hosting choices |
| Editing | Who will update pages after launch | Determines whether you need training or a simpler editor |
| Content volume | Number of pages, posts, galleries, products, or downloads | Directly affects build time and structure |
| Maintenance | Who will handle updates, backups, and support | Impacts ongoing costs and responsibility |
For public-facing organisations in the UK and Ireland, it is also worth reading the official guidance on accessibility statements on GOV.UK and the Irish accessibility guidance. The point is not to turn a normal enquiry call into a compliance lecture. The point is to know what kind of site you are asking someone to build.
Questions to ask about WCAG 2.2 and accessibility statements
WCAG 2.2 is the latest version of the Web Content Accessibility Guidelines. In plain English, it adds a few more checks that help real people use the site without friction. Three of the most practical additions are:
- Target size — clickable controls should be large enough to tap accurately.
- Accessible authentication — login steps should not depend on traps people cannot get through without a workaround.
- Consistent help — if help is offered, it should be easy to find in the same place across pages.
Ask the designer:
- Which WCAG level are you building toward?
- Will accessibility be considered in the design, content, and testing stages?
- How will form labels, focus states, and error messages be handled?
- If we publish PDFs or reports, how will those be made accessible?
- Will you help us prepare an accessibility statement if we need one?
If your organisation publishes documents, the Irish government’s guide to making accessible documents is worth a careful read. A PDF that looks neat on a desktop can still be unreadable in the wrong tools. That is the sort of small failure that becomes a large support problem.
Questions to ask about performance
Performance is not only a developer concern. It changes how people feel about the site. Slow pages look heavier, less reliable, and less worth waiting for. That matters for product pages, donation forms, service enquiries, and any page where visitors need confidence.
Use these questions:
- How will images be sized, compressed, and delivered?
- Will you use modern image formats where appropriate?
- What is the plan for scripts from plugins, embeds, and third-party tools?
- How do you check loading speed on mobile, not just desktop?
- Will the build be tested for layout shifts and interaction delays?
- What hosting setup do you recommend for the expected traffic?
Google’s web.dev overview of the Core Web Vitals is a plain-language starting point if you want to understand the terms behind the numbers. You do not need to memorize acronyms. You do need to know that a quote should cover the work required to keep the site stable, responsive, and usable on real devices.
How to compare quotes fairly
Web design quotes often look comparable when they are not. The cheapest number may leave out accessibility testing, content migration, image optimisation, or post-launch support. Ask what is included, what is assumed, and what is definitely excluded.
- Scope — how many templates, page types, or revisions are included?
- Accessibility — is testing part of the build or left as a later add-on?
- Performance — is image compression, caching, and script cleanup part of the work?
- Training — will someone show you how to make updates safely?
- Support — what happens after launch if something breaks?
- Exclusions — what is not covered, even if the quote sounds complete?
A quote that states its boundaries clearly is worth more than a vague promise with a shiny total. Clarity is a feature. It just does not fit in a sales slogan.
A simple first-call template
You do not need a long brief to start well. You need the right facts in the right order.
Hello, I am looking for a quote for a new website / redesign. The site needs to:
- serve [business / artist / charity goal],
- include [pages or sections],
- support [forms, bookings, donations, ecommerce, downloads],
- work well on mobile,
- meet accessibility expectations from the start,
- and stay fast enough to feel reliable.
I have [content ready / content in progress / content to be written], and I would like to know what is included in your quote, what is not included, and what you need from me to give an accurate estimate.
If you are ready to talk through a project, the easiest next step is to contact us with the site’s goals, content, and any accessibility or performance needs you already know about. If you want more practical guidance first, browse the blog for related planning notes.
Accessibility and performance are not extras anymore. They are the conditions that make the rest of the website worth building.
HTML
)