Start scanning free

( Compliance )

The business case for accessibility

Accessibility expands your market, reduces legal risk, improves SEO and cuts support costs. The numbers behind each claim, and where to start.

Accessibility is usually pitched as compliance. The stronger case is commercial: around 16% of people live with significant disability, accessible sites rank and convert better, legal exposure is growing on three continents, and retrofits cost multiples of building it right. Accessibility is margin protection, not charity.

The market you’re turning away

The WHO puts significant disability at about 1.3 billion people worldwide. In most developed markets that’s roughly one in six of your potential customers — before counting the broken wrist, the missing glasses, the bright sunlight, the noisy train. Accessibility features are used far beyond their target population: captions, keyboard shortcuts and high-contrast modes are mainstream conveniences.

An inaccessible checkout doesn’t offend these users; it simply loses them. They buy from the competitor whose form works with a screen reader, and no analytics dashboard tells you why.

  • United States: ADA web accessibility lawsuits have run at thousands of filings per year for years, hitting e-commerce hardest. Settlements plus forced remediation under deadline is the expensive way to reach the same destination.
  • Europe: the European Accessibility Act applies to e-commerce, banking, transport and more — private sector, not just government. EN 301 549 (which incorporates WCAG) is the reference standard.
  • Australia: the Disability Discrimination Act has covered websites since Maguire v SOCOG in 2000. Government procurement expects WCAG conformance, and complaints against private organisations succeed.

Every regime converges on the same technical baseline — WCAG AA. Meeting it once answers all of them.

The SEO and AI search dividend

Search engines and AI systems read structure, not pixels — the same structure assistive technology depends on. Semantic headings, alt text, descriptive link text, transcripts and captions are ranking inputs and WCAG requirements. As answers move into AI experiences, machine-readability compounds: accessible pages are the ones AI systems can quote.

You can fund the accessibility work from the SEO budget with a straight face. It’s the same work.

The engineering economics

The cost curve is steep in the wrong direction:

  • At design time, accessibility is mostly decisions: token contrast, focus states, label placement. Near-zero marginal cost.
  • At build time, it’s habits: semantic elements, wired labels, alt text in the CMS workflow.
  • After launch, it’s archaeology: auditing thousands of pages, refactoring component libraries, retraining teams — often under a legal deadline.

Industry rules of thumb put retrofit cost at several multiples of build-time cost, and that matches what we see: a component fixed once in a design system fixes a thousand pages; the same fix applied page-by-page after a demand letter is a project.

There’s a quality dividend too. The most common failures — unlabelled controls, broken heading structure, keyboard traps — are defects by any definition. Teams that catch them ship better interfaces for everyone.

Procurement: accessibility as a sales asset

If you sell software, accessibility is now revenue-side. Government, education and enterprise buyers ask for a VPAT/ACR during procurement, and “we don’t have one” reads as “we haven’t thought about this”. Vendors with a current, honest conformance report clear a filter their competitors fail.

Making the case internally

Skip the moral framing if it hasn’t landed; run the numbers that fit your business:

  1. Revenue: sessions × 16% × your conversion value = the traffic you’re serving a degraded experience.
  2. Risk: one demand letter or failed enterprise deal typically exceeds a year of accessibility tooling and fixes.
  3. Efficiency: cost of fixing a component in the design system now vs. every page later.

Then make the first step small: scan your five highest-traffic pages, fix the criticals, and put scanning in the workflow so the fixes stick. Accessibility fails as an annual event and succeeds as a habit — the business case is really the case for the habit.

Frequently asked questions

How many people are affected by web accessibility?

The World Health Organization estimates about 1.3 billion people — roughly 16% of the global population — live with significant disability. Add temporary impairments and situational limitations, and the share of sessions affected by accessibility barriers is far larger.

Does accessibility improve SEO?

Substantially, through overlap. Semantic headings, alt text, descriptive links, captions and fast keyboard-navigable pages are simultaneously accessibility requirements and search signals. The same work moves both.

What is the legal risk of an inaccessible website?

It depends on jurisdiction, but the trend is one-directional. US ADA web lawsuits run at thousands of cases a year, the European Accessibility Act now applies to a broad range of digital services, and Australian organisations face complaints under the Disability Discrimination Act. Remediation under deadline costs far more than building it right.

Where should a team start with accessibility?

Scan your highest-traffic pages, fix the critical automated findings first (alt text, labels, contrast, headings), then add accessibility checks to your development workflow so regressions get caught when they're introduced. Audit-once-a-year is how sites drift back out of conformance.

AI Search Does accessibility affect Google rankings? AI Search Why accessibility matters for AI search Product Design Accessibility mistakes product teams make