The Accessibility Demand Letter: What It Says, and What To Do Before It Arrives

It arrives on law-firm letterhead, and its structure is nearly standard by now. A statement that your website was tested and found inaccessible to users with disabilities. Citations to the Americans with Disabilities Act, and to WCAG 2.0 as the measuring stick. A list of specific failures. Missing alt text. Keyboard traps. Unlabeled forms. Contrast violations. And an offer to settle, with remediation promises and fees attached. The letter is not the reason to do this work. It is just the invoice for not having done it.

Hundreds of organizations received a version of this letter last year, and the trend is steep. Web accessibility lawsuits and demand activity sped up sharply through 2015. Retail, banking, and hospitality. And, with particular energy, higher education. There, the Education Department’s civil-rights office has been resolving complaints against universities in agreements that read as sector-wide notice.

We have written about accessibility as craft, as audience, and as quality engineering since our WCAG 2.0 explainer in 2010. This post is about accessibility as legal exposure. That is the frame many readers will meet it in this year, and the frame deserves careful handling before the panic vendors supply their version.

The legal landscape, in working summary

The essentials, put plainly. The usual reminder applies: we are practitioners, not counsel.

The ADA’s application to websites has never been settled by regulation. The Department of Justice has signaled for years that web accessibility falls within the statute. It has repeatedly put off the formal rulemaking that would specify standards, most recently pushing its timeline again.

That vacuum is the engine of the current wave. With no regulation, private plaintiffs and settlements are defining the working standard. The standard they have converged on is WCAG 2.0 Level AA. The same benchmark careful teams have built to since 2010, cited in nearly every settlement and consent decree that matters.

Courts have split on questions like whether a website must connect to a physical place of business, which is why sector exposure varies. But the trend across venues is expansive. For higher education the analysis is simpler and stricter. Federal funding duties under Section 504, and state versions of it, reach digital properties without the physical-nexus debate.

‘We didn’t know’ has no weight anywhere in this landscape. ‘We are working from a plan’ has a great deal, which brings us to the defensible position.

The defensible position: audit and plan, then progress

Who gets sued, who settles at a high price, and who resolves matters with little fanfare: the pattern is readable in the case history. It supports a working rule we have repeated in every risk talk this year. Plaintiffs’ firms target inaction, not imperfection.

No institutional site of real size is flawless against WCAG 2.0 AA, and perfection is not the standard anywhere. What sets apart the defensible organizations:

A genuine audit. Automated tooling catches roughly the machine-checkable third. Missing alt text, contrast, labels. Human review with keyboard and screen reader covers the interaction and structure failures where the serious barriers live.

A ranked remediation plan. Template-level fixes first, because they repair every page at once. User-impact and traffic weighting after that.

Documented, dated progress against it.

And an accessibility statement with a working feedback channel. It serves users and shows good faith.

Organizations holding those four artifacts answer a demand letter with a file rather than a scramble. The difference is priced in every outcome we have watched. The letter’s arrival is largely a bet that no file exists. Make the bet a loser in advance.

What to do this quarter, sequenced

• Commission the honest audit, scoped to your key user flows and templates, with findings ranked by user impact rather than by tool output count. The tool report with four thousand unsorted errors is a document, not a plan.

• Fix at the template layer first. The structural failures live in templates and components, and fixing them repairs the site wholesale. Navigation, forms, focus handling, heading structure. Our design-system practice pays here directly. Governed components mean accessibility fixes spread on their own.

• Put content-team habits in the program. Alt text, heading use, link language, and document accessibility are ongoing editorial habits. That makes training and CMS guardrails (required fields, accessible defaults) half the durable program, per the editor-training coverage.

• Publish the statement, staff the channel, keep the log. The statement commits to the standard and invites reports. The channel gets answered. The log becomes the progress record that converts ‘defendant’ into ‘organization already doing the work’ in every conversation that matters.

The economics, since someone will ask for them

The budget talk follows the risk talk as surely as the letter follows the neglect. So, the numbers as we have watched them run.

The reactive path prices out like this. Settlement and legal fees: the published settlements run well into five and six figures before any fixing. Plus fixes done at emergency speed, the most costly way to do any technical work, per every rush project we have ever quoted. Plus the consent-decree monitoring and reporting duties that can run for years. Plus the press coverage that arrives when a university or public institution is named in an accessibility suit.

The proactive path prices out like this. An audit measured in weeks. Template fixes folded into work your team was already doing. The redesigns, the component updates, the CMS moves where accessibility rides along at marginal cost. That is why it belongs in the discovery phase. And the training-and-governance layer, which costs less per year than one month of the reactive path’s legal meter.

We have now run this comparison honestly for enough clients to state it as a finding rather than a sales pitch. The proactive program is cheaper in every case we have priced, before counting the audience gains. The gap widens every year the lawsuit curve steepens. The stakeholder who calls accessibility a cost center is reading the wrong column.

The reframe, which has not moved since 2010

Close with the position we will keep restating as the lawsuit coverage grows louder. The legal frame, handled alone, produces exactly the wrong program. The checkbox retrofit, done resentfully, decaying at once.

The same work that cuts legal exposure expands your audience. Disability rates are far larger than most stakeholders assume, before counting the situational and aging cases. The work improves the site for everyone. The semantic structure, keyboard operability, and clarity WCAG demands are quality engineering under another name, and the same investments keep paying off in search and mobile. And for the mission-driven institutions we serve, it is simply the mission applied to the front door.

Do the work because it is good work, on a schedule you chose, funded as the practice our discovery-phase practice prescribes rather than the emergency the letter would make it. The letter you never receive is the bonus, and it is, this year more than ever, a bonus worth engineering. The audit calendar is open. January is a fine month for it.