Best Accessibility Tools After a Demand Letter

A demand letter changes what a tool has to do. Before the letter, a scan that finds problems is enough for most owners. After the letter, the tool also has to leave a record: what was found, when it was found, what was changed, and how the change was checked. That record is what a lawyer can read, and it is what a second reader can check later.

This is general information, not legal advice. If you have received a demand letter or been sued, talk to a qualified attorney.

What a demand letter usually asks for

A demand letter is not a lawsuit. It is a written notice that says a site has barriers for people with disabilities and asks for fixes, often by a date in the letter. The letter often names specific pages and specific problems, such as missing alt text, unlabeled form fields, low contrast, empty links, or pages that cannot be used with a keyboard alone. Read the letter for three things before you buy anything: the pages named, the problems named, and the date given for a reply.

Do not delete the named pages to make the problem go away, and do not reply with promises about dates or fixes before a lawyer has read the letter. Save a copy of each named page as it looks now, note the date you received the letter, and pass the letter to a lawyer on the same day if you can. A tool bought in a hurry can still help, but only if it fits the sequence in the next section.

The first week: order of work

Start with advice, not software. A lawyer reads the letter, checks whether the claims match your site, and decides what the reply should say. While that review runs, you can start the technical side in parallel, because the technical side takes time and the lawyer will want facts, not guesses.

First, run a scan of the named pages and save the report with its date. Second, check each named barrier by hand: move through the page with a keyboard only, listen to the page with a screen reader if you have access to one, and look at the contrast of the text the letter names. Third, write a short fix list that pairs each barrier with the page, the fix, and the date the fix is due. Fourth, fix in source code where you can, retest the same pages, and save the second report beside the first. The pair of reports, before and after, is the core of a dated record.

A tool that only adds a floating panel on top of the page does not fit this sequence well, because it leaves the source code unchanged. The barriers the letter names are still in the code when the panel is switched off or when its script fails to load. A tool that changes code, or that gives a developer exact fix values to apply, fits the sequence because the second scan can show the code itself changed.

Five kinds of tool, and what each one leaves behind

1. A free scan for the first read

A free scan answers a narrow question fast: what does an automated check find on one page right now? Axeazy's free scan runs in 60 seconds with no signup and no card, and the scan on the homepage covers the page you enter. Use it for a first read of a named page, then save the result with the date. Do not treat a free scan as a full answer. A free scan checks one page, or a homepage only on some plans, and automated checks miss problems that only a person using a keyboard or a screen reader will catch. The United States Department of Justice guidance makes the same point: automated checkers can help, but a clean report does not mean everything is accessible, so pair a manual check with automated checks.

2. A code fix tool for sites with a developer or a repo

For a site with its own GitHub repository, the strongest fit is a tool that sends fixes as a real pull request with a visible code diff that the owner or developer reviews and merges. That diff is evidence in itself: it shows the old code, the new code, and the date of the change. Axeazy works this way for repo sites, using 98 automated checks against WCAG 2.2 AA and grouping fixes into 14 categories, from alt text and form labels to heading structure and landmark structure. Every scan and fix is recorded with a date and time, and reports can be exported as a PDF. That dated record is the part a lawyer can put beside the letter and the reply.

For WordPress sites, Axeazy's free plugin applies three render-time fixes: a skip navigation link, a page language attribute, and an alt text fallback, with no account needed. Paid plans add weekly scans and further fixes. For Shopify stores and other sites with no repo, Axeazy scans the site and gives a guided checklist with computed fix values to apply by hand. That distinction matters after a demand letter, because a Shopify owner should not expect automatic template changes from a scan, and should plan developer time for the checklist instead.

3. A manual audit for the full picture

A manual audit is a person testing sampled pages against WCAG 2.2 AA with a keyboard, a screen reader, and visual checks, then writing findings mapped to specific criteria. It costs more and takes longer than a scan, and it finds problems a scan cannot see, such as a label that exists but says the wrong thing, or a checkout step that traps keyboard focus. Accessible.org lists most of its manual audits at $1,250 to $2,750, at $100 to $250 per primary page and $25 to $100 per light page, with technical support at $195 per hour. Those figures are from its pricing page, checked October 31, 2026, and a quote for your site will depend on how many templates and user paths are in scope.

After a demand letter, an audit fits best when the letter names many pages, when the site has a checkout or booking path, or when a lawyer wants a dated report from a person rather than a scan alone. Ask what the audit covers before you pay: which pages, which criteria, whether retesting after fixes is included, and whether the report gives a developer exact steps for each finding.

4. A monitoring tool for staying fixed

Fixes decay. A theme update, a new plugin, or a new product page can bring back an old barrier in a week. A monitoring tool reruns checks on a schedule and alerts you when new problems appear, so the next scan is not a surprise. Axeazy runs weekly monitoring on paid plans. When you compare monitoring tools, ask which pages are covered, how often checks run, whether old reports stay available with their dates, and whether alerts go to a person who can act on them. A monitoring report with no owner is a file nobody reads.

How to choose in one pass

Ask four questions, in this order. Does the tool change source code, or only add a layer on top of the page? Does it leave a dated record of each scan and each fix that a lawyer can read? Does it cover the pages the letter names, including forms and checkout steps, or only the homepage? And does it include a retest after fixes, so the second report proves the first problems are gone?

Price comes after those four. Axeazy's paid plans are listed at about $29 a month for Starter, about $79 a month for Pro, and about $199 a month or $1,799 a year for Agency, with paid prices shown at checkout and an annual saving of 20 to 25 percent. Check the plans on Axeazy's pricing page before you decide, because prices can change. A manual audit at $1,250 to $2,750 is a one-off cost that buys depth, while a monthly tool buys repeat checks and a running record. Many owners after a letter need both: an audit for the full picture, and a tool for the fixes and the weekly record.

One limit to plan around: Axeazy does not scan PDFs, so a letter that names PDF menus, forms, or documents needs a separate plan for those files. Colour contrast is also handled with care: the scan detects contrast problems and calculates a correct colour, but a visible colour change is never applied without owner approval. That approval step is worth keeping, because a colour change touches brand and design, and a lawyer will want to see that the owner chose it.

Related reading

Read the earlier guide on website accessibility lawsuit statistics for 2026 for the filing counts behind the current climate, and the buyer guide on how to choose an accessibility tool for ten checks to run before signing. For the letter itself, Axeazy's demand letter guide walks through the same first steps in a shorter form.

• Overlay vs Code Fixes: Which Should You Buy?

FAQ

What should I do first after receiving a demand letter?

Pass the letter to a qualified attorney before you reply, save copies of the named pages as they look now, and note the date you received the letter. Then run a dated scan of the named pages so the lawyer has facts about what is actually there, rather than a guess about what the letter means.

Does a tool fix a demand letter by itself?

No tool by itself resolves a legal notice. A tool finds barriers, helps fix code, and leaves a dated record, while a lawyer handles the reply, the timetable, and any agreement. Treat the tool as the technical half of the response and legal advice as the other half.

Should I install a widget the day the letter arrives?

Pause before adding any new layer to the page. A layer that sits on top of the page does not change the source code the letter names, and it can add a second thing to explain later. Fix the named barriers in code first, or get a dated scan and a fix plan first, and let the lawyer advise on timing.

Last checked: October 31, 2026 Sources: ADA.gov web guidance; W3C WCAG 2.2; Accessible.org pricing page; accessibility.com demand letter guide; xsibility demand letter response guide; Axeazy capabilities and pricing pages.

Run Axeazy's free 60 second scan on a named page and save the dated report for your lawyer.