Accessible Website Design Best Practices

Accessible Website Design Best Practices is a practical question with consequences for budget, schedule, quality, and the people responsible for approving the finished work. This guide treats it as a real project decision rather than a keyword: what the work involves, where the trade-offs sit, what information changes the answer, and what to check before anything is published or delivered.

The details below are written for business owners, marketing teams, producers, and practitioners working with web design & development. Use the workflow, cost ranges, review checks, examples, and questions as a working brief. The right answer depends on the material, audience, channel, volume, and deadline, so those variables stay visible throughout instead of being hidden behind a universal recommendation.

Who this is actually for

If you're reading about Accessible Website Design Best Practices, you're usually in one of three places: something went wrong and you want to know why, something is coming up and you want to get it right, or someone has quoted you a number and you want to know whether it's reasonable.

Any of those is a fine reason to be here. What follows covers the whole thing: what the work involves, what it costs in the US, how long it takes, what we need from you, and how to tell whether what comes back is any good. Skip to whichever part you need.

When occasional turns into ongoing

There's usually a moment when web design & development stops being something you handle between other things and starts being a job. It tends to look like this:

• The work is landing on someone whose actual job is something else, and their actual job is slipping.
• Volume has stopped being occasional and started being weekly.
• Quality varies depending on who happened to be free that day.
• You are turning down opportunities because production cannot keep up.
• The same fix keeps getting made because nobody wrote down how to do it right.
• You are paying for software seats that get used a few days a month.

If two or three of those are true, the question isn't really whether to get help. It's whether to hire, to use a freelancer, or to work with a studio — and there's a section further down that lays out the trade-offs honestly, including the cases where hiring us is the wrong answer.

The words people will use at you

Every field has vocabulary that gets deployed as a shortcut and lands as a barrier. Here's what the common terms in web design & development actually mean, in plain English. You shouldn't need this to buy the work, but it makes the conversation shorter.

Core Web Vitals

Google's three published page-experience measurements: how fast the main content appears, how quickly the page responds to input, and how much the layout jumps around.

LCP

Largest Contentful Paint. How long until the biggest thing on screen has loaded. Under 2.5 seconds is the published "good" threshold.

INP

Interaction to Next Paint. How long the page takes to visibly respond when someone taps or clicks. Under 200 milliseconds is good.

CLS

Cumulative Layout Shift. How much the page moves around while it loads. Under 0.1 is good, and the usual cause of a bad score is an image with no dimensions.

Semantic HTML

Using the element that means the thing — a button for a button, a heading for a heading. It is what makes a page navigable by screen reader and legible to a crawler.

Responsive design

One layout that adapts to the screen it is on, rather than a separate mobile site.

CMS

Content management system. The admin area where someone who does not write code changes the words.

Headless

A setup where the content lives in one system and the front end is built separately. More flexible, more moving parts, more expensive to run.

Progressive enhancement

Building so the core works without JavaScript, then layering improvements on top. It is why a well-built form still submits when a script fails to load.

Redirect map

The list that says where every old URL now points. The thing that decides whether a redesign keeps its search traffic or throws it away.

There's a fuller reference library if you want to go deeper on any of these, and everything in it is written the same way — plainly, with sources.

How the work actually runs

A web design & development job runs in stages, and the stages aren't interchangeable. Here they are in the order they have to happen.

1. Discovery

We find out what the site is for, who it is for, and what has to be true for it to count as working. Usually a couple of calls and a look at whatever analytics already exist. The goal is a one-page statement of the job that both sides recognize.

2. Content and structure

What goes on the site, and how someone finds it. This comes before design on purpose: laying out boxes before anyone knows what fills them is how you end up with a beautiful page that cannot hold your actual content.

3. Design

Wireframes, then visual design, usually starting at phone width. Most of your visitors are on a phone, and a layout that works small almost always scales up more gracefully than one that has to be squeezed down.

4. Build

Front-end code, templates, and the content management setup. Built semantically so the markup means something to a screen reader and a search engine, not just to a browser.

5. Content load

Real copy and real images, not placeholder text. This is where most schedules slip, and almost always on the client side, so it is worth starting during the build rather than after it.

6. Testing

Real devices, keyboard navigation, screen reader, slow connection. Plus the boring stuff: forms actually sending, redirects actually redirecting, analytics actually recording.

7. Launch

DNS, certificates, redirects from every old URL, search console verification. The redirect map is the part people forget, and it is the part that costs traffic.

8. Aftercare

Watching the first few weeks of real traffic, fixing what only real use reveals, and handing over enough documentation that you are not dependent on us to change a phone number.

Where does Accessible Website Design Best Practices fit? Usually somewhere in the middle of that sequence, and it inherits every decision made before it. That's the argument for settling scope early: a change at stage two is a conversation, and the same change at stage seven is a rebuild.

What to send us

A brief doesn't need to be long. It needs to be specific about a handful of things, and vague about everything else is fine.

What belongs in the brief

Who it is for

The audience, in one sentence, in your own words. Not a persona document — a sentence.

What it has to do

The action you want someone to take, or the decision you want them to be able to make.

Where it will live

Every placement, at every size. This is the single most common omission, and it is the one that causes reshoots and recrops.

What already exists

Brand guidelines, prior work, the files nobody likes. Especially the files nobody likes, and why.

What is fixed

Colors, typefaces, legal copy, platform requirements, anything that is not up for discussion.

What good looks like

Two or three references, plus one example of something you actively dislike. The dislike is more useful than the likes.

The real deadline

The date something has to be live, not the date you would like to see a draft. Say which one you are giving.

Who signs off

One name. A brief with four approvers and no decider is a brief that will cost you two extra revision rounds.

Two of those deserve emphasis, because they're the ones that cost money when they're missing. Where it will live — every placement, at every size — is the omission that causes reshoots and recrops. And who signs off is the one that quietly adds revision rounds: a project with four approvers and no decider will always cost more than one with a single name on it.

If you've got files ready now, you can send them straight over — they go to private storage rather than to an inbox, and nothing is public. If you'd rather see the standard before committing to anything, try us on a couple of files first. No card, no commitment, and if it's not what you need you've lost nothing but an afternoon.

How to check what comes back

Most revision rounds exist because of how the previous round was reviewed, not because of how the work was done. Here's how to make a review count.

Check it where it will live

Approve a web asset in a browser, a print asset on paper, an audio mix on a phone speaker. Approving a deliverable in the tool that made it is how problems reach the public.

Check the edges, not the middle

The middle is almost always fine. Look at the corners, the smallest size, the longest string, the darkest area, the last ten seconds.

Check one thing at a time

Color, then type, then spacing, then content. A review that tries to see everything at once sees the loudest thing and misses the rest.

Collect feedback before you send it

One consolidated list beats six emails. Contradictions inside your own organization are cheaper to resolve on your side than on ours.

Be specific about what is wrong

"Make it pop" costs a revision round. "The headline is hard to read against the sky, can we darken the area behind it" costs ten minutes.

Say what is right too

Not out of politeness. If you only flag problems, the next round can lose the thing you liked without anyone knowing it mattered.

The bar we hold ourselves to

So you know what you're measuring against, here's what gets checked on our side before anything reaches you. None of it is optional, and none of it is charged as an extra.

• Core Web Vitals measured on real devices: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1
• Every interactive element reachable and operable by keyboard alone, in a sensible order
• Text contrast at 4.5:1 for body copy and 3:1 for large text, checked rather than assumed
• Tested on an actual mid-range Android phone, not just a desktop browser window made narrow
• Forms tested end to end, including what happens when they fail
• Every old URL either still works or redirects once, with no chains

You can see how we present finished work — including the before and after — in the portfolio. Anything marked as a sample is our own demonstration piece rather than a client project, and it says so on the item.

Three situations you might recognize

Abstract advice is easy to agree with and hard to use. These are the shapes this kind of problem actually arrives in, and what we'd do about each one.

A redesign that lost half its traffic

The new site launched with new URLs and no redirect map. We rebuilt the map from the old sitemap and server logs, redirected every old address to its nearest match, and resubmitted. Most of the traffic came back over six to ten weeks. None of it needed to have gone.

A site nobody could update

Every text change was a developer ticket, so the site quietly went stale. We rebuilt the templates around editable regions with guardrails, so the marketing team can change copy and images without being able to break the layout.

Fast on a laptop, unusable on a phone

The site was tested on the workstation that built it. On a mid-range Android on a normal connection it took eleven seconds to become usable. Compressing images, deferring third-party scripts and dropping two unused font weights got it under three.

None of those needed heroics. They needed somebody to look at the right thing early, which is most of what experience buys you in this field.

What it costs in the US

Here's what this generally costs in the United States. Treat it as a sanity check rather than a price list: the honest number depends on the job, and anyone who gives you a firm price without looking at the work is guessing.

Those are wide ranges, and they're wide for a reason. Here's what moves a job from one end to the other.

What actually drives the price

Number of unique templates

A fifty-page site with six templates is a much smaller job than a twelve-page site with eleven. Count layouts, not pages.

Content readiness

A site with copy and images ready moves at roughly twice the speed of one where content is written during the build.

Integrations

A CRM, a booking system, a payment gateway, a legacy inventory feed. Each one is a separate contract with somebody else's API and somebody else's outage.

Accessibility target

Meeting WCAG 2.1 AA from the start adds modestly to design and build. Retrofitting it later costs several times more.

Migration

Moving a thousand existing pages, preserving their URLs and their formatting, is its own project with its own risks.

Who maintains it

Building something you can edit safely costs more up front than building something only we can change. It is almost always the cheaper of the two over three years.

How the money is usually structured

Separately from how much, there's the question of how. Five models cover almost everything in this industry, and the right one depends on how well the job can be described before it starts.

Per unit

A fixed price per image, per minute, per page, per asset. Best when the work is genuinely repeatable and you can describe one unit precisely. It is the easiest model to budget and the easiest to argue about, because everything hinges on whether your idea of one unit matches ours. Settle that on a sample before you settle it on an invoice.

Hourly or day rate

You buy time, and the output is whatever that time produces. Honest when nobody can scope the job yet — a rescue, an unknown archive, an exploratory phase. Ask for a not-to-exceed number anyway. An open hourly arrangement with no ceiling is a budget with no floor.

Fixed project fee

One number for a defined scope, usually with a stated number of revision rounds. The model most clients prefer and the one that punishes a vague brief hardest. The fee is only fixed if the scope is, so expect the scope document to be more specific than feels comfortable. That specificity is what protects you.

Monthly retainer

A set amount of capacity reserved for you every month. Worth it once the work is continuous rather than occasional — a catalog that refreshes, a channel that publishes weekly, a site that keeps changing. Below roughly ten to fifteen hours a month it usually costs more than buying the work as it comes.

Value or outcome based

Pricing tied to a business result rather than to effort. Rare, and rarely as clean as it sounds. It works where the outcome is unambiguous and attributable, and falls apart where it is neither. Treat an outcome-based proposal with the same scrutiny you would give any other claim about attribution.

If you want a real number rather than a range, the fastest route is to send us the actual brief — scope, volume, deadline, and a couple of sample files if you have them. That's usually enough for a fixed price rather than an estimate.

How long it takes

How long should this take? Here are the usual durations, with the caveat that every one of them assumes decisions get made when they're asked for.

One thing worth saying plainly: the most common cause of a late project isn't production. It's waiting — for content, for a decision, for one person to look at something. If you want a project to move quickly, the highest-leverage thing you can do is name one person who can say yes and make sure they're available. That single change is worth more than any amount of chasing.

Rush work is possible and it's genuinely more expensive, because it means real people working real overtime or a job jumping a queue somebody else is in. We'll always tell you what a rush actually costs before you commit to it.

In house, freelance, studio, or a model?

This is the decision underneath "how much does it cost", and it deserves a straight answer rather than a pitch. There are four ways to get web design & development work done, and we're only the right choice for some of them.

Keep it in house

Someone on your payroll does it.

What's good about it: Fastest feedback loop there is, deepest product knowledge, no briefing overhead for small changes.

What's not: You are buying a person, not a job: their vacation, their sick days, their ceiling, and the software. It stops making sense the moment demand is spiky, because you pay for the peak all year.

Hire a freelancer

One specialist, engaged directly.

What's good about it: Cheapest way to buy real expertise, and you get the actual person who does the work.

What's not: One person is one point of failure. No cover, limited throughput, and if they move on mid-project you inherit their files and their conventions.

Use a studio

A team with a process, a review layer and cover.

What's good about it: Handles volume and variety, carries the QC step, and does not disappear when one person is sick.

What's not: More expensive per hour than a freelancer, and you are one client among several. Worth it when consistency across a lot of output matters more than the lowest rate.

Use a model

Generative or automated tooling, with or without a person checking.

What's good about it: Genuinely fast and genuinely cheap on the parts it is good at, and it does not get tired on page four hundred.

What's not: It is confidently wrong in ways that are hard to spot at a glance, and the parts it fails at are the ones a client notices: hands, text, counts, edges, continuity. Nothing should ship without a person having looked at it, which is why our AI work is priced with the review included rather than as a discount.

The short version: if the work is constant and central to what you do, hire. If it's spiky, or it needs a range of skills you can't justify employing, use a studio. If it's one specialist thing and you've found the right specialist, use them. We'd rather tell you that up front than take on a job we're the wrong shape for.

The US rules worth knowing

This isn't legal advice and we're not lawyers. It's a list of the American rules that come up often enough in this kind of work that not knowing about them gets expensive. If any of it applies to you, it's worth twenty minutes with someone who is a lawyer.

ADA and Section 508

US courts have read Title III of the Americans with Disabilities Act to cover many commercial websites, and federal agencies and their contractors are bound by Section 508, which adopts WCAG as its technical standard. In practice that means designing to WCAG 2.1 AA and being able to show your work.

State privacy law

California, Colorado, Virginia, Connecticut and a growing list of other states have consumer privacy statutes with their own notice and opt-out requirements. If your site collects anything, the privacy notice and the cookie behavior are engineering decisions as much as legal ones.

FTC disclosure

The Federal Trade Commission expects material connections and paid endorsements to be disclosed clearly and close to the claim. That is a design problem: a disclosure nobody can see is a disclosure that does not count.

And the general commercial stuff

Whatever the discipline, buying professional services in the United States raises the same handful of questions. These are the ones clients ask us most.

Contracts and statements of work

A statement of work that names the deliverables, the number of revision rounds, the ownership terms and the payment schedule is worth the hour it takes to read. Most disputes in this industry are not about quality; they are about two people having understood "done" differently.

Ownership and work made for hire

Under US copyright law, work created by an independent contractor generally belongs to the contractor unless there is a written assignment or it falls into one of the narrow statutory work-made-for-hire categories. That surprises a lot of buyers. Get the assignment in writing; any studio that hesitates is telling you something useful.

Paying an outside supplier

A US business paying a US contractor normally collects a Form W-9 and may need to file a 1099-NEC; paying a non-US supplier usually means a W-8BEN or W-8BEN-E instead. Your accountant will want these before the first invoice, not after the last one.

Sales tax on services

Whether a creative or digital service is taxable varies by state, and several states tax some digital deliverables and not others. It is worth one question to your accountant before a large engagement rather than one letter from a state revenue department after it.

Advertising claims

The Federal Trade Commission holds advertisers responsible for claims made in their marketing, including claims made in images. A retouched product photo that no longer represents the product is an advertising problem before it is a design one, and the liability sits with the advertiser rather than the retoucher.

Accessibility

Title III of the Americans with Disabilities Act has been read by US courts to cover websites in many circumstances, and federal agencies and their contractors are bound by Section 508, which points at WCAG. Accessibility is cheaper designed in than litigated out.

Our own terms are published rather than sent on request: you can read the terms and conditions, the payment terms, the refund policy and the confidentiality and NDA position before you talk to anybody. If something in them doesn't work for you, say so early — most of it is negotiable and all of it is better settled before the work than after it.

Questions to ask anyone quoting for this

Including us. If a supplier gets cagey about any of these, that's the answer to the question you were actually asking.

Who is actually doing the work?

Ask whether it stays with the person you are talking to, moves to a team, or gets subcontracted. None of those is wrong. Not knowing is.

What exactly is a revision?

Ask what counts as a revision versus a new brief, and how many are included. This is the single most common source of a bill you did not expect.

Who owns the output?

Get it in writing, including the working files. "You own the final" and "you own everything" are very different positions, and the second one costs more for a reason.

What happens if it is wrong?

Ask what a redo costs and how fast it happens. A studio with a clear answer has had the conversation before.

Can I see work like mine?

Not a showreel — work in your category, at your volume, with the constraints you have. A beautiful portfolio in another category proves taste, not fit.

How do you handle my files?

Where they are stored, who can reach them, how long they are kept, and what happens at the end. If you are sending anything unreleased, get this in the contract.

What do you need from me?

A supplier who cannot answer this has not thought about your side of the job, and you will discover that at the deadline.

One more, and it's the one people are most embarrassed to ask: what would make you turn this job down? A studio that has never turned work away is a studio that takes everything, and that tells you something about how carefully it's going to be handled.

Working with a studio you'll never meet

Most web design & development work now happens between people in different places and often different time zones. That's fine — it's been fine for years — but it rewards a few habits and punishes a few others.

Overlap, not coverage

What matters is not whether a supplier is awake at 2pm Eastern, but whether there is a predictable window when you can both talk. Ask for the window and put it in the calendar.

Batch your feedback

Across a time difference, three rounds of one comment cost three days. One round of twelve comments costs one. This is the single biggest lever you have on turnaround.

Send files once, properly

A clean handoff with originals, a written brief and named files saves more time than any amount of chasing. Half of all "slow" projects were slow at the start.

Agree what "urgent" means

Everyone says urgent. Agree in advance what a rush actually triggers — a different queue, a different price, a different set of hands — so the word keeps its meaning.

Keep one thread

A decision made in a direct message is a decision nobody else on either side can find. One channel, one thread per job.

Our hours overlap the US business day, and we'd rather agree a standing window with you than promise round-the-clock availability nobody can actually sustain. If you want to talk it through before committing to anything, get in touch — there's no pitch deck and nobody will chase you.

Putting this guide into practice

Start with the decision named in the title, write down the outcome you need, and collect one real example of what success and failure look like. Then use the workflow and review criteria above to compare options consistently. If the scope still cannot be stated clearly, a short discovery step is more useful than asking several suppliers to guess at a fixed price.

For help applying this to a live project, review our Web Design & Development services or send the brief for a scoped recommendation.

More useful paths

Use these paths to continue with the closest practical topic, service, or decision guide.

• Web Design & Development article library
• Real Estate Website Design Best Practices
• Hotel Website Design Trends and Best Practices
• AI-Powered Website Personalization: The Future of UX
• AI Chatbots for Websites: Are They Worth It?
• E-commerce Development vs Website Design