Website accessibility for small business: a practical 30-day plan
If you run a small or mid-size business with a website, here is the legal picture in plain English, the problems that show up most often, and a four-week plan you can start this week.
The short version
| Which law? | Title III of the Americans with Disabilities Act covers “places of public accommodation.” Courts have increasingly applied it to business websites, especially online stores and sites tied to a physical business |
|---|---|
| Is there a small-business exemption? | Not for Title III as such. The obligations depend on the facts, so size alone does not exempt you |
| What standard? | The DOJ has not published a technical rule for private business websites. In practice courts, settlements and demand letters point to WCAG 2.1 Level AA, and increasingly WCAG 2.2 AA |
| The usual risk | A demand letter or lawsuit that cites common, easily detected problems, followed by legal fees and a deadline to fix the site |
| The practical answer | Fix the common problems, test with a keyboard, check your vendors’ tools, keep records and rescan regularly |
General information, not legal advice. Laws and court decisions differ by state and circuit and change over time. If you receive a demand letter or lawsuit, speak to an attorney experienced in ADA cases.
Why small businesses get targeted
Accessibility problems on a website are often easy to find with automated software. Plaintiffs’ firms use that software to find sites with obvious barriers and send demand letters in volume, so a business does not need to be large or well known to be on the list.
The numbers keep growing. Seyfarth Shaw’s ADA Title III tracker counted 3,117 federal website accessibility filings in 2025, up 27% from 2,452 in 2024. UsableNet, a vendor that tracks both federal and state suits, reports more than 5,000 in 2025, with roughly 70% aimed at e-commerce and retail sites. These counts come from different sources with different methods, so treat them as a direction, not an exact figure.
The problems that show up most often
The WebAIM Million, an annual automated check of the top one million home pages, found detectable WCAG failures on 95.9% of home pages in 2026. The three most common were:
- Low-contrast text, on 83.9% of home pages. Light gray text on white is the classic example.
- Images with no alt text, on 53.1%. Screen readers have nothing to say about them.
- Form fields with no label, on 51%. This often hits search boxes, newsletter signups and checkout fields.
All three are cheap to fix compared with the cost of a dispute, and a scan finds them in minutes.
A 30-day plan
Week 1: find out where you stand
- List your key pages: home page, top landing pages, contact form, and every step of your checkout or booking flow.
- List your third-party tools: payment forms, scheduling widgets, chat, maps, review plugins and anything embedded from another company. Their problems appear on your site.
- Run a scan of those pages and save the report. It is also your starting record.
- Pick an owner: one named person who is responsible for accessibility.
Week 2: fix the common problems
- Make text contrast at least 4.5 to 1 for normal text and 3 to 1 for large text.
- Add short, meaningful alt text to every informative image. Mark purely decorative images as decorative.
- Give every form field a visible label that is programmatically connected to it.
- Make link text specific. “Read our pricing” works, “click here” does not.
- Give each page a unique title and set the page language.
Week 3: test with a keyboard and at 200% zoom
- Put your mouse aside and use only Tab, Shift+Tab, Enter, Space and the arrow keys. Can you reach and use every menu, button, form and checkout step?
- Make sure the focused item is always visible, and that sticky headers, cookie banners and chat widgets do not cover it.
- Check that headings run in a logical order, and that there is a “skip to main content” link.
- Zoom to 200% and on a phone-sized window. Nothing should require scrolling in two directions or overlap.
- Watch or caption any video, and provide a transcript for audio.
Week 4: vendors, documentation and habits
- Ask your vendors whether their product meets WCAG 2.1 AA and request an accessibility conformance report (often called a VPAT or ACR). Keep the answers.
- Publish an accessibility statement that says what standard you aim for, how to report a problem, and how to reach a real person. Then respond to what comes in.
- Add a pre-publish check for new pages, images, PDFs and emails: alt text, headings, link text, contrast, a labeled form.
- Rescan on a schedule, at least quarterly and after every redesign or major plugin update.
- Keep a log of what you found, what you fixed and when. A dated record of good-faith work is useful if a complaint arrives.
Why an overlay is not a fix
Some vendors sell a widget or “overlay” that promises to make a site compliant with one line of code. These tools can adjust surface features, but they generally do not repair the underlying problems such as heading structure, keyboard focus order or unlabeled fields, and sites using them have still been sued. In January 2025 the U.S. Federal Trade Commission ordered one overlay vendor, accessiBe, to pay $1 million over claims that its AI product could make any website compliant. Treat an overlay, at most, as an extra feature, not as your plan.
If you receive a demand letter
- Do not ignore it, and do not pay or sign anything immediately.
- Contact an attorney with ADA website experience. Your general business lawyer may not handle these.
- Save the letter, the date it arrived and your scan reports and fix log.
- Start fixing the problems it names. Remediation helps in almost every outcome.
What an automated scan can and cannot do
A scan reliably finds issues such as missing alt text, unlabeled fields, low contrast and invalid structure. It cannot judge whether alt text is meaningful, whether a checkout makes sense with a screen reader, or whether a custom widget is usable by keyboard. Those need a person. Use a scan to find and track the common problems, then test the important flows by hand. A scan result is not a certificate of compliance.
Check your site with WCAGScan
WCAGScan checks your pages against WCAG 2.0, 2.1 and 2.2 and reports each issue with the criterion, the affected element and a suggested fix. The free scan covers up to 5 pages, with no account needed. See pricing.
Sources
- Seyfarth Shaw: ADA Title III news and insights
- WebAIM: The WebAIM Million
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- ADA.gov
- UsableNet reporting on 2025 digital accessibility lawsuits; U.S. Federal Trade Commission, January 2025 order against accessiBe