Website Accessibility: Reach More Customers and Reduce Risk
Website accessibility in plain English: WCAG essentials, the 1-in-4 disability market, lawsuit trend data, fixes ranked by effort and the overlay trap — with a 90-day plan.
One in four adults in the United States lives with a disability, according to the CDC — which means roughly a quarter of the people landing on your website right now face barriers most teams never notice. Failing contrast on a price tag, a checkout that traps keyboard users, an unlabeled form field: each one quietly removes customers. And since 2023 those barriers increasingly arrive with a legal price attached.
This guide translates WCAG — the Web Content Accessibility Guidelines — into plain English, sizes the market you are missing, and walks through audits and fixes ranked by effort. Every number is attributed to its source or labeled as an illustrative model, and everything ends in a 90-day plan you can run without pausing your roadmap. No overlays, no fear-mongering, no legal advice — just the business case and the work.
Here is the short version before the details.
Key Highlights
- 1 in 4 US adults — about 61 million people — lives with a disability (CDC), and they visit your site whether you designed for them or not.
- Americans with disabilities control an estimated $490 billion in discretionary spending (American Institutes for Research); with friends and family, the global figure reaches $13 trillion (Return on Disability Group).
- 95.9% of the world's top one million home pages had detectable WCAG failures in WebAIM's 2024 scan — down only from 98.1% in 2020.
- 4,605 digital accessibility lawsuits were filed in the US in 2023 (UsableNet), with roughly 4,000 more in 2024 — e-commerce the target in about four out of five cases.
- 71% of users with disabilities click away from a site they find hard to use, and 82% would spend more with an accessible one (Click-Away Pound survey).
- The DOJ now requires WCAG 2.1 Level AA for state and local government web content by April 2026 or 2027 — the clearest signal yet of where the standard sits.
- More than 800 accessibility professionals signed an open letter warning that overlay widgets cannot deliver compliance on their own.
- Our illustrative mid-size retailer model shows about USD 82,000 in first-year value against roughly USD 34,500 of one-time fixes.
Reason 1: A Quarter of Your Market Is One Barrier Away From Leaving
Start with the people, not the law. 26% of US adults — about 61 million people — live with a disability, according to the CDC, and prevalence rises steeply with age: by the time your customers reach 65, roughly 2 in 5 are affected.
Prevalence breaks into groups, and each group maps to a design problem you can name:
For a retailer, the arithmetic is blunt. If 26% of adults live with a disability and 71% of them click away from a site that is hard to use (Click-Away Pound survey), then roughly 18 of every 100 visitors are one frustrating contrast ratio away from your competitor. The same survey found 82% would spend more with a company whose site was accessible.
Northgate Optical, the six-store eyewear retailer we will follow through this article, sells prescription glasses online and in store. Its buyers skew 45 and older — the exact demographic where vision, mobility and dexterity disabilities concentrate. When the owner first saw these numbers, her reaction was the right one: this is a customer problem first and a legal problem second.
Key takeaway: Accessibility is market share wearing a legal jacket. A quarter of adults, a 71% click-away rate and $490 billion in US discretionary spending (American Institutes for Research) make the opportunity case before any lawyer does.
Reason 2: The Web Is Still Mostly Broken — WCAG in Plain English
WebAIM's annual Million report scans the home pages of the world's top one million websites. In 2024, 95.9% had detectable WCAG failures — down from 98.1% in 2020, which tells you the web is improving at a glacial pace while lawsuits accelerate.
WCAG is the technical standard behind nearly every law, settlement and demand letter. It is organized around four principles — content must be Perceivable, Operable, Understandable and Robust, nicknamed POUR. Level AA is the conformance target referenced by the DOJ, the EU and virtually every US settlement; AAA is aspirational for most businesses.
Here is what the four principles mean when you stop reading specifications and start looking at your own site:
| WCAG principle | Plain-English test | What it catches on a real site |
|---|---|---|
| Perceivable | Can every visitor perceive every piece of content? | Low-contrast text, missing image alt text, videos without captions |
| Operable | Can every visitor use every control? | Menus that trap keyboard users, invisible focus indicators, timed carousels |
| Understandable | Does the site behave predictably? | Vague error messages, labels that vanish, jargon-only instructions |
| Robust | Will it work with assistive technology? | Missing form labels, invalid HTML, custom widgets invisible to screen readers |
The failures WebAIM found most often are the same ones that annoy every user, disabled or not:
| Most common failure (WebAIM Million 2024) | Share of home pages | Business damage | Typical fix effort |
|---|---|---|---|
| Low-contrast text | 81% | Invisible pricing, abandoned reading, bounce | Days |
| Missing image alt text | 55% | Lost SEO, blank screen-reader experience | Days |
| Missing form input labels | 49% | Abandoned forms, wrong data entry | Days to weeks |
| Empty links (no discernible text) | 45% | Screen-reader chaos, lost navigation | Days |
| Empty buttons | 28% | Dead checkout and filter buttons | Days |
WCAG 2.2, a W3C Recommendation since October 2023, added criteria on focus states, tap targets and drag-and-drop alternatives — treat 2.1 AA as the floor and 2.2 as the trend line.
Key takeaway: If 96% of home pages fail and the failures are mundane — contrast, alt text, labels — accessibility is not exotic engineering. It is a short list of known defects you can start fixing this month.
Reason 3: The Lawsuit Trend Makes This a Budget Line, Not a Debate
UsableNet's annual counts of digital accessibility lawsuits filed in US courts tell a one-directional story. There were 4,055 suits in 2021, 3,255 in 2022 and a record 4,605 in 2023, with roughly 4,000 more in 2024 — an average near 90 filings a week at the 2023 peak. About four out of five target e-commerce, and the majority land in New York and California courts.
Regulators are moving in the same direction as the plaintiffs' bar. In April 2024, the US Department of Justice finalized a rule requiring WCAG 2.1 Level AA for state and local government web content — deadlines land in April 2026 for larger entities and April 2027 for smaller ones. Private businesses fall under ADA Title III, where courts use WCAG as the practical standard; the EU's European Accessibility Act applies to e-commerce from June 2025.
What does getting sued actually cost? Published case reports vary widely, but the legal line items alone often exceed what the whole remediation would have cost. Typical ranges we see across engagements (illustrative, not legal advice):
| Cost item | Typical range (USD, illustrative) | Notes |
|---|---|---|
| Responding to a demand letter | $5,000–$15,000 | Attorney review, remediation plan, negotiation |
| Settlement | $8,000–$25,000 | Plus a consent agreement with deadlines |
| Defense if litigated | $25,000–$75,000+ | Multi-month; fees accrue regardless of outcome |
| The remediation itself | $10,000–$40,000 | You pay this in every scenario — with or without the lawsuit |
Repeat targets are common, too — UsableNet has reported businesses facing five or more suits in a single year. A settlement that fixes nothing invites the next letter; a genuine remediation ends the cycle.
Key takeaway: The lawsuit math is asymmetric. For most mid-size businesses, full remediation costs less than one litigated defense — and unlike legal fees, it pays back through customers you were previously turning away.
Step 1: Audit Before You Touch a Single Line of Code
Resist the urge to start fixing the contrast issues you spotted by eye. A proper audit gives you the full defect list, ranked by how badly each issue blocks users and how expensive each is to fix. Skip it and you will treat symptoms while the checkout stays broken.
Automated scanners are the first pass, and you should know their limit: published tool comparisons put their coverage at roughly 30–40% of WCAG issues, because most real barriers require judgment. A complete audit layers four techniques:
- Automated scans across your key templates — home, category, product, cart, checkout, forms.
- Keyboard-only walkthroughs of every money path: can a user complete a purchase with Tab, Enter and Escape alone?
- Screen-reader passes with NVDA (free, Windows) or VoiceOver (built into macOS and iOS) on the same flows.
- Zoom and contrast checks at 200% magnification, plus color-blindness simulation on your brand palette.
When Northgate ran this process, the audit surfaced 93 issues — 38 under Perceivable, 27 under Operable, 19 under Understandable and 9 under Robust. Seven issues completely blocked checkout for keyboard or screen-reader users, including a prescription-upload widget that was invisible to assistive technology. Nobody on staff had ever tried to buy glasses without a mouse.
We took the same build-from-scratch approach for a healthcare client that needed patient-facing accessibility on day one — documented in our healthcare patient app case study. Building it right initially is always cheaper than retrofitting; our business website checklist includes the accessibility pass for refresh projects.
Key takeaway: Automated tools find only 30–40% of the problems. The defects that actually cost you customers — keyboard traps, unlabeled controls, invisible upload flows — are found by humans testing like the humans with disabilities you are trying to serve.
Step 2: Fix by Effort — Days, Weeks, and Months
Not all fixes are equal, and sequencing is where budgets survive or die. The 93 Northgate issues split cleanly: 40 fixable in days and 53 requiring project work. Sort your own list the same way before anyone writes an estimate.
| Tier | Typical fixes | Effort | Northgate examples (illustrative) |
|---|---|---|---|
| Quick wins (days) | Contrast, alt text, form labels, link text, heading order, focus indicators | One sprint, one developer | Repaint 460 low-contrast elements; label 23 form fields; add alt text to 180 product images |
| Structural (weeks–months) | Checkout and menu keyboard traps, custom widgets, modal focus, date pickers | Developer project with testing | Rebuild the prescription-upload flow; fix address autocomplete for screen readers |
| Ongoing (process) | Editorial standards, QA gates, acceptance criteria | Governance, not code | Accessibility checklist on every ticket; quarterly content-team training |
Two things surprised the Northgate team. First, the quick wins moved real users within a week — support calls about "I can't read the price" simply stopped. Second, the same checkout that trapped keyboard users also lost touch users on small phones — a conversion problem with nothing to do with disability. Accessible structure and good mobile UX are largely the same work.
That overlap shows up in booking flows too — we rebuilt a retreat-booking engine where keyboard traps and an unoperable date picker were costing reservations (booking engine case study). If a rebuild is coming anyway, our website redesign guide shows how to make accessibility a requirement, not a phase-two wish.
Key takeaway: Ship the days-tier first — it is cheap, fast and moves real customers. Then budget the structural tier honestly; retrofitting widgets is where the real cost lives, and pretending otherwise is how projects stall.
Step 3: Measure the Payback — It Is Bigger Than Risk Avoidance
For Northgate, we modeled the first-year return with assumptions visible enough to argue with. Online revenue was USD 1.9 million on roughly 40,000 monthly sessions; if 26% of visitors face a disability barrier and 71% of those click away, a large share of sessions was at risk. Recapturing even a slice — through a fixed checkout, labeled forms and readable pricing — plus SEO gains from 180 newly labeled product images produced the modeled result below.
The SEO line is the quiet compounding one. Alt text, semantic headings, descriptive links and logical structure are exactly what search crawlers reward — accessibility and rankings overlap so heavily that we track them together, as in our Core Web Vitals publishing case study where structure fixes lifted both metrics. Support savings are smaller but permanent: clear error messages and labeled fields generate fewer help calls.
Key takeaway: Model the return before you approve the budget — recovered orders, SEO value and support hours, not just avoided lawsuits. At Northgate's scale, roughly USD 82,000 in modeled first-year value against USD 34,500 of one-time fixes pays for the program twice.
Mistake 1: Buying the Overlay Shortcut
Overlays are third-party scripts that promise instant WCAG compliance: paste a code snippet, pay a monthly fee, watch the badge appear. They work by rewriting your page in the visitor's browser — auto-generating alt text, forcing contrast, patching labels. For a few narrow issues they genuinely help; for the structural barriers that block checkout, they cannot reach the underlying code.
The professional consensus is blunt. More than 800 accessibility practitioners, developers and users of assistive technology signed an open letter urging the industry to stop marketing overlays as compliance solutions. Lawsuits regularly name sites wearing overlay badges — the most practical proof available that a badge is not a shield.
Where overlays claim and fail, in one table:
| Overlay claim | Reality on a real site |
|---|---|
| "Instant WCAG compliance" | Compliance is a property of your code; a script can label what it can see, not rebuild what it cannot |
| "Protects you from lawsuits" | Plaintiffs name overlay-badge sites routinely; a badge is evidence of awareness, not remediation |
| "Fixes images and videos" | Auto-generated alt text guesses at meaning — a wrong description is worse than none |
| "Cheaper than remediation" | Subscriptions run for years; remediation is largely one-time, and you own the result |
If an overlay is already installed, do not rip it out mid-contract or mid-dispute — but stop treating it as the program. Let a real audit set the remediation agenda.
Key takeaway: There is no product you can buy that makes a site accessible; there is only work, most of it one-time. Anyone selling otherwise is selling the feeling of compliance — the one thing lawsuits do not accept.
What Your Business Should Do
Here is the 90-day plan we hand clients, sized to run alongside normal work:
Days 1–30: See your site as your customers do.
- Run an automated scan across your key page templates, then do a keyboard-only pass of your main money path — checkout or lead form.
- Pull 90 days of analytics: devices, browsers, top entry pages and where visitors abandon.
- Collect two audit quotes, and ask each bidder exactly how they test with keyboards and screen readers — not just scanners.
Days 31–60: Fix the highest-frequency, highest-impact issues.
- Ship the quick-win tier: contrast, alt text, form labels, link text, heading order, visible focus states.
- Fix your checkout or lead flow end-to-end for keyboard and screen-reader users — this is where lawsuits and lost orders both live.
- Add accessibility acceptance criteria to your design and development templates so new work does not recreate old debt.
Days 61–90: Prove it and lock it in.
- Re-test every fix, then document the remaining backlog with an owner and a date against each item.
- Publish an accessibility statement with a feedback channel, and respond to every piece of feedback you receive.
- Schedule a quarterly re-audit and train everyone who touches content on the basics.
The Bottom Line
Website accessibility is one of the few projects that pays out on three ledgers at once: more customers from a quarter of the market that currently bounces, stronger SEO from the same fixes, and lower legal exposure in a market that filed nearly 90 suits a week at its peak. What separates the businesses that benefit from the ones that get letters is simply whether the audit ever became a project.
If you want a second pair of eyes on where your site stands, that is a routine week for us. Book a free strategy call and we will walk your top pages against this checklist — or send us a message and we will answer within one business day.
Free download: the Learning Guide (PDF)
Everything worth keeping from this article — key numbers, tables and the action checklist — in one print-ready, fillable PDF.
Join our newsletter — more growth tips, twice a month
Playbooks from real projects. No spam, unsubscribe anytime.
FAQ
How much does it cost to make a website accessible?+
Costs scale with site size and how much structural work exists. For a typical mid-size site, our illustrative ranges run USD 5,000–10,000 for an audit, USD 5,000–8,000 for quick-fix remediation and USD 15,000–25,000 for structural work such as checkout rebuilds. Small brochure sites land far lower; complex custom applications run higher.
Is WCAG compliance legally required for my business?+
For private businesses in the US, no single statute says "WCAG 2.1 AA", but ADA Title III lawsuits use WCAG as the de facto standard, and the DOJ codified it for government entities in April 2024. The EU's European Accessibility Act applies WCAG-derived requirements to e-commerce from June 2025. Practically, AA is the target that demand letters, settlements and courts expect. This article is not legal advice — confirm specifics with your counsel.
Do accessibility overlays make a website compliant?+
No. Overlays patch some surface issues in the visitor's browser but cannot fix structural barriers — keyboard traps, broken widgets, missing flow logic — and more than 800 professionals signed an open letter against their compliance marketing. Lawsuits routinely name sites with overlay badges installed. A remediation program built on a real audit is the only approach that survives scrutiny.
How long does an accessibility remediation project take?+
Quick wins — contrast, alt text, labels, focus states — ship in days to two weeks. Structural fixes such as checkout rebuilds and custom widget repairs typically run six to twelve weeks including assistive-technology testing. The ongoing tier is a process rather than a project: quarterly re-audits and accessibility gates in your development workflow. Our illustrative Northgate plan covered roughly one quarter for the full first pass.
Engineering-led team at Emerson Technology — building apps, web platforms and growth systems for ambitious businesses. Every guide comes from real client work.