Home

Services

SEO Services Social Media Website Development AI Automation About Reviews Portfolio Blog Contact Free Website Audit
Website Development in the United States

In the US, Accessibility Is a Build Requirement, Not a Preference

Most website briefs treat accessibility as something to improve later, if there is budget. In the United States that reading is out of step with what the Department of Justice actually says: “The Department has consistently taken the position that the ADA applies to web content.” That single sentence moves accessibility from the nice-to-have column into the specification, and it is far cheaper to build for than to retrofit.

No credit card required · 30-minute call · No obligation to sign up

12+ years in digital marketing Working with the USA businesses
✓ You Own The Code — No Lock-In ✓ Quoted & reported in USD ($) ★★★★★ Trustpilot 5.0 ★★★★★ Google 4.9
Times Square in daylight, yellow cabs and lit advertising boards on Seventh Avenue
DOJ position on the ADA and the webApplies
Standard the DOJ points toWCAG
The Numbers First

Six things a US build has to answer for

None of these is about design taste. All six are obligations or constraints that a US site is expected to meet, and most of them are cheap at build time and expensive afterwards.

  • The ADA applies to web contentDOJ’s own words · not a vendor’s claim
  • WCAG is the referenced standardAlong with Section 508 · per the DOJ
  • Privacy law is state by stateNot one rule · several, and they differ
  • Buyers compare before contactingPricing and proof pages do the qualifying
  • Reviews are checked, not skimmedThird-party proof, not testimonials you wrote
  • Mobile is the majority, not the fallbackAnd the desktop still has to be right

The first two rows are worth reading together, because they are frequently reported as vaguer than they are. The DOJ says the ADA applies to web content and points at the Web Content Accessibility Guidelines and the Section 508 Standards as the guidance for meeting it. What that gives a build is a target — contrast ratios, keyboard operability, labelled form fields, alternative text, sensible heading order. All of them are ordinary work if they are in the specification, and all of them are a retrofit if they are not. This is not legal advice and we do not give any. It is a description of what we build to and why.

Straight Talk

An accessibility overlay is not the same as an accessible site

The tempting answer, sold heavily in the US, is a widget: a script you add to the page that claims to make the site conform. It is attractive because it is cheap and immediate, and it does not do what an accessible build does. An overlay sits on top of the markup that is already there. If the headings are in the wrong order, the form fields are unlabelled and the contrast is too low, those things are still true underneath — and the people who actually use assistive technology are the ones who find out first.

What works instead is unglamorous and mostly free at build time. Semantic markup rather than divs pretending to be buttons. Form fields with real labels. Colour contrast checked while the palette is being chosen rather than after it is signed off. A page that can be operated entirely from the keyboard. Alternative text written by somebody who looked at the image. None of that is expensive when it is in the specification, and all of it is expensive as a remediation project.

The second US-specific complication is privacy, and it is genuinely awkward: there is no single federal rule, so what a site must do about data depends on which states its visitors are in. In practice that pushes a build toward the stricter interpretation rather than the minimum, because a site that satisfies the more demanding states satisfies the rest, and maintaining several behaviours is worse than maintaining one.

The last thing is commercial rather than legal. American buyers compare openly and early — four or five vendors, pricing pages read, review sites checked — before anybody makes contact. That means a US site does its qualifying before the first conversation, and the pages that do that work are the ones agencies most often leave until last: pricing, process, proof, and a straight answer about who you are not for.

  • ✓The DOJ position is explicit — "The ADA applies to web content." That is a specification, not an opinion piece.
  • ✓Overlays do not fix markup — A widget on top of bad structure leaves the structure bad. The users affected notice first.
  • ✓Contrast belongs in the palette decision — Checked while colours are chosen. Free then, a redesign afterwards.
  • ✓Privacy is state by state — Build to the stricter reading — one behaviour is cheaper to maintain than several.
  • ✓The site qualifies before the call — Pricing, process and proof. The pages most often left until last.
Times Square at night, taxis and a traffic officer beneath the billboards

An accessibility overlay does not change the markup underneath it. The people who rely on assistive technology are the ones who discover that, and they discover it first.

.
Ghalib Ashrafi Founder & Digital Strategist · 12+ years across search, social & web

What a US build actually involves

Six things, and the first two are in the specification rather than in a later phase.

01

WCAG in the Specification

Semantic markup, keyboard operability, labelled fields, real alternative text and heading order — agreed before design rather than audited after launch, which is when it becomes a remediation project.

02

Contrast Decided With the Palette

Checked while colours are being chosen, because a brand palette that fails contrast is a brand problem discovered at the worst possible moment — after everything has been signed off.

03

Privacy Built to the Stricter Reading

Consent, data handling and retention designed once, to satisfy the more demanding states rather than the minimum. Several behaviours cost more to maintain than one.

04

Pricing and Proof Pages

The pages that do the qualifying before anyone calls, and the ones most often postponed. US buyers compare four or five vendors before making contact, and the site is what they compare.

05

Performance on Real Devices

Mobile is the majority of US traffic and the desktop still has to be right. Both get tested on what people actually use rather than on the machine the site was built on.

06

Documented Handover

What was built, to what standard, and how to keep it that way — including the accessibility decisions, so the next person does not undo them without knowing.

WCAGThe standard the DOJ points to
12+Years building and maintaining sites
4Services run by one team
USDQuoted, invoiced and reported

What clients say

Real clients, quoted in their own words — published with their permission.

More of them, in full, on our reviews page.

— Our Proprietary Methodology —

The Visibility Framework™, applied in the USA

The method doesn’t change by market. What it’s pointed at does.

Step 01

Audit & Discovery

What the current site earns, where it leaks, what your competitors do better, and what the new one must achieve. Ends in a written scope and a fixed price — not an estimate that grows.

Step 02

Structure & Design

Sitemap, wireframes and user journeys agreed before decoration, then a design system applied consistently. You approve the shape before we make it beautiful.

Step 03

Build & Test

Front end, back end, CMS and integrations, on a staging site you can see from day one. Tested on real devices, real screen readers and real slow connections.

Step 04

Launch & Improve

Redirects verified, analytics connected, handover recorded — then we look at what real visitors actually do and fix what the design assumed wrongly.

Honest, No-Nonsense Commitment

The price we quote after discovery is the price you pay — if we underestimated the work, that is our problem, not a change request. And on any rebuild, if organic traffic drops because of something we did at migration, we fix it at our cost, however long it takes.

Investment

Website Development pricing for the USA, in USD

Quoted per build in dollars. Accessibility done properly is not a line item here because it is not an add-on — it is how the markup gets written. What it does affect is honesty about timelines: getting it right the first time is faster than a remediation pass, and considerably cheaper.

Starter

A marketing site, built to standard.

$3,000 – $6,000
  • WCAG-aware markup from the start
  • Contrast decided with the palette
  • Consent and data handling designed in
Get a Quote

Enterprise

Multi-site or heavily integrated.

$18,000+
  • Dedicated senior developer
  • Accessibility review across an estate
  • Custom integrations and ongoing support
  • Optional: combine all 4 services for full-funnel growth
Get a Quote

Every plan is scoped around your market — get a free audit and we’ll recommend what fits, priced in USD.

What you’re actually committing to

Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.

  • A fixed price, agreed before we startQuoted after discovery, not estimated on a call. If the work takes longer than we thought, that is our risk — the price does not move unless you change the scope.
  • 50% to begin, 50% at launchNo large upfront payment held for months, and nothing owed until the site is live and you have seen it working.
  • You own everythingDomain, hosting, code repository, design files and content — all in your name from day one, and still yours if we never work together again.
  • No proprietary lock-inStandard, widely-used technology only. Any competent developer can take the site over, and nothing stops working because you stopped paying us.
  • Two rounds of revisions per stageIncluded at wireframe and design stage, where changes are cheap. Beyond that, or after sign-off, changes are quoted before any work starts.
  • 30 days of support after launchBugs and small tweaks included as standard. A care plan afterwards is optional, never automatic, and cancellable with 30 days’ notice.

These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.

the USA Website Development questions, answered

Does the ADA really apply to our website? +
The Department of Justice’s published position is that it does: "The Department has consistently taken the position that the ADA applies to web content", and it points at the Web Content Accessibility Guidelines and the Section 508 Standards as the guidance for meeting it. We build to that standard for US clients as a matter of course. What we do not do is tell you what your legal exposure is — that is a question for a lawyer, and anyone selling you a website who answers it is answering the wrong question.
You can, and it will not do what an accessible build does. An overlay sits on top of the markup that already exists — if headings are in the wrong order, fields are unlabelled and contrast is too low, all of that is still true underneath. The people who actually rely on assistive technology find that out first, and a widget does not stop them finding out.
At build time, close to nothing, because it is mostly about how the markup is written rather than extra features — semantic elements, real labels, keyboard operability, alt text somebody actually looked at the image to write. As a remediation project on a finished site it is a different order of expense entirely, which is the whole argument for putting it in the specification.
There is no single federal rule, so what applies depends on where your visitors are. In practice we build to the stricter reading rather than the minimum: a site that satisfies the more demanding states satisfies the rest, and maintaining one behaviour is considerably cheaper than maintaining several that diverge over time.
Different questions entirely. The SEO page is about geography — US search being decided at metro level rather than nationally. The social page is about platform mix, and the fact that Pinterest sends more referral traffic than Instagram here. This page is about what a US build has to answer for. Many clients take more than one; they are quoted and run separately by the same team.
No. Our head office is in Karachi and we would rather say that here than list a virtual address. Karachi is roughly nine to ten hours ahead of US Eastern, so our working day overlaps your morning — a real, scheduled window rather than a claim about a 24-hour desk we do not have.
Keep Exploring

Related Website Development pages

Same service, different angle — by market, by discipline and by platform.

Get A Free Accessibility Check

Send us the site and we will tell you what fails on contrast, keyboard operability and labelling — and what it would take to fix rather than cover up.

Ready to build to the standard rather than around it?

Free 30-minute audit · No obligation · Response within 24 hours

Get in touch with Ghalib Ashrafi HQ

Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.

↑
Phone / WhatsApp: +92 343 2653224
Email: info@ghalibashrafi.com
Hours: Mon–Sat, 10am–7pm (PKT)
Still deciding? Get a free website audit — no obligation. Get Free Audit