The Real Cost of an Inaccessible Website: Penalties, Lawsuits and Lost Contracts
Most organisations discover accessibility law through a demand letter or a failed procurement questionnaire. Both are avoidable, and both are cheaper to prevent than to answer.
Accessibility is usually presented as an ethical argument, occasionally as a market-size argument, and almost never as what it has actually become: a legal and commercial exposure that arrives without warning, in an envelope or a procurement questionnaire.
This article sets out the real cost structure of non-compliance — and it is not a single fine.
Four distinct forms of exposure
| Exposure | How it arrives | What it costs |
|---|---|---|
| Private litigation and demand letters | A claim citing specific technical barriers on your site | Legal fees, settlement, mandated remediation on someone else's timetable |
| Regulatory enforcement | Authority investigation following complaints | Statutory penalties, consent decrees, ongoing reporting |
| Procurement exclusion | A conformance report requested during tender | The contract, silently, with no explanation given |
| Market exclusion | Users who cannot complete the journey | Revenue you never see in analytics because the funnel never started |
Organisations plan for the first and are usually destroyed commercially by the third — because losing a tender produces no headline and no incident report.
The United States: ADA and Section 508
Web accessibility claims under the Americans with Disabilities Act have grown into a routine, high-volume area of practice. Two features matter for planning. First, the typical defendant is not a household-name enterprise but a mid-market business, because the same handful of technical defects — missing alternative text, unlabelled form fields, keyboard-inoperable menus, insufficient contrast — can be identified at scale and cheaply. Second, most matters settle, which means the cost is legal fees plus a remediation programme executed under deadline pressure rather than a courtroom judgment.
Separately, Department of Justice enforcement carries statutory civil penalty maximums for ADA violations, which are periodically adjusted for inflation, and Section 508 governs federal procurement: agencies and their suppliers must meet accessibility standards that reference WCAG. If you sell to US public bodies, conformance is a precondition, not a differentiator.
Europe: the European Accessibility Act
The EU has taken the market-access route rather than the litigation route. Under the European Accessibility Act, a range of products and services — including e-commerce, banking, transport and e-books — must meet accessibility requirements to be placed on the EU market. Enforcement sits with national authorities, and penalties are set per member state, which means exposure is local, varied and difficult to model centrally. The public-sector Web Accessibility Directive already imposes conformance and reporting duties on public bodies and, by extension, their suppliers.
The practical consequence for a non-EU business is simple: EU customers bring EU obligations.
The cost nobody records: failed procurement
Every large public body and an increasing number of enterprises request an Accessibility Conformance Report during tender. Suppliers who cannot produce one either withdraw or complete it optimistically and lose credibility later. We have reviewed procurement processes where accessibility was a pass/fail gate and the excluded suppliers were never told why they scored zero on a criterion they did not know existed.
This is the most expensive form of non-compliance and the only one with no legal notice attached.
Why the cheap fixes are not fixes
The overlay widget industry exists because the promise — one line of JavaScript, instant compliance — is exactly what a nervous marketing director wants to hear. It does not work. Overlays cannot repair semantic markup, focus order, accessible names or authorisation-gated flows; they frequently conflict with the screen reader configuration a user has spent years tuning; and their presence has not prevented claims. Several overlay vendors have themselves been the subject of complaints. Treat them as a liability disclosed on your own site.
What actually reduces exposure
- Audit against WCAG 2.2 AA with manual testing. Automated tools reliably surface roughly a third of issues; keyboard-only and screen reader testing find the ones that block real users.
- Fix at component level. One inaccessible date picker used on ninety pages is one defect, not ninety. Design-system remediation is both cheaper and durable.
- Prioritise by journey, not by page count. Registration, search, checkout, account management and support contact carry the exposure.
- Publish an honest accessibility statement with a known-issues list and dated remediation commitments. Demonstrated, evidenced progress is a far stronger position than an unverifiable claim of full conformance.
- Bind your vendors. A third-party booking widget, chat tool or payment iframe can break your conformance without a line of your code changing. Require conformance reports contractually.
- Prevent regression in CI. Accessibility checks on the component library, plus keyboard operability in the definition of done, stop the audit cycle from repeating annually.
The commercial argument, stated plainly
Every intervention above improves the product for everyone. Clear form errors reduce checkout abandonment. Keyboard operability speeds up power users. Semantic markup improves how search engines and AI assistants extract your content. Captioned video produces indexable text. Accessibility is the rare compliance obligation whose remediation work you would want to fund anyway — which makes deferring it until a demand letter arrives an unusually poor trade.
Knowing where you actually stand
The first question to answer is not "are we compliant?" but "what would an audit find on our five highest-revenue journeys?" That answer takes days to produce and changes how urgent everything else feels.
Kinematic Digital runs WCAG 2.2 AA audits combining automated scanning with manual keyboard and screen reader testing, then fixes the defects at design-system level so one correction propagates across every template. See our UX and accessibility services and web development practice, or request an accessibility audit.
Frequently Asked Questions
What are the actual penalties for an inaccessible website?
Exposure comes in three forms rather than one fine. In the United States, private ADA lawsuits and demand letters produce settlement and legal costs, while Department of Justice enforcement carries statutory civil penalty maximums that are periodically adjusted for inflation. In the EU, national authorities enforce the European Accessibility Act with penalties set per member state. Separately, public-sector procurement simply excludes non-conforming suppliers.
Is a small business really at risk of an accessibility lawsuit?
Yes. The majority of ADA web claims target small and mid-size businesses, not large enterprises, because standard technical defects are cheap to identify at scale and settlements are quicker than litigation.
Does an accessibility overlay widget protect us legally?
No. Overlays do not repair underlying markup, focus order or semantics, they frequently interfere with assistive technology users have already configured, and their use has not prevented claims. Several have themselves been the subject of complaints.
What standard do we have to meet?
WCAG 2.2 Level AA is the practical target recognised by courts, regulators and procurement processes. In Europe, EN 301 549 wraps WCAG and extends it; US federal procurement uses Section 508, which references WCAG.
What is the fastest way to reduce legal exposure?
Fix the highest-impact defects on your top user journeys, publish an honest accessibility statement with a dated remediation plan, and document your programme. Demonstrable, evidenced progress is a materially stronger position than silence or an unverifiable claim of full compliance.