Website Accessibility for Small Businesses: ADA Risk, WCAG and Costs
What small businesses should know about website accessibility in the U.S.: ADA exposure, WCAG basics, practical fixes, how much it costs and why overlay widgets are not enough.
Website accessibility means building a site that people with disabilities can use, including people who rely on screen readers, keyboard navigation, captions or high contrast. In the United States there is no single federal rule that spells out technical requirements for every private business website, but lawsuits and demand letters under the Americans with Disabilities Act have been brought against businesses of many sizes, and courts and agencies commonly look to the Web Content Accessibility Guidelines (WCAG) as the practical benchmark. Building accessibly from the start is usually cheaper than repairing a site afterward, and it helps all visitors. This guide explains the basics, the costs and what to ask your provider.
Why it matters
Roughly one in four U.S. adults reports having some type of disability, according to the Centers for Disease Control and Prevention. Many of these people use the web every day, and an inaccessible site can block them from booking, buying or reading essential information. There is also a legal side. Title III of the Americans with Disabilities Act applies to places of public accommodation, and many courts have heard cases claiming that business websites are covered, although the legal theories differ by jurisdiction. The Department of Justice has expressed its view that the ADA applies to the web, and in 2024 it issued a final rule setting technical requirements for the websites and apps of state and local governments, pointing to WCAG 2.1 Level AA. That rule applies to governments, not to private businesses, but it shows where expectations are heading. Check the Department of Justice's accessibility pages for current developments, including compliance dates.
What WCAG is
The Web Content Accessibility Guidelines are published by the World Wide Web Consortium. They are organized around four principles, often summarized as POUR:
- Perceivable: information must be presented in ways users can perceive, for example text alternatives for images and captions for video.
- Operable: the site must work with a keyboard and give users enough time and clear navigation.
- Understandable: text should be readable and forms should be predictable, with helpful error messages.
- Robust: the code should work with assistive technologies such as screen readers.
WCAG has conformance levels A, AA and AAA. Level AA is the one most commonly cited as a target for business sites.
Common problems and fixes
| Problem | Who it affects | Typical fix |
|---|---|---|
| Images without alternative text | Screen reader users | Add short descriptive alt text; leave decorative images empty |
| Low color contrast | People with low vision or color blindness | Use sufficiently contrasting text and background colors |
| Menus or forms that need a mouse | Keyboard-only users | Make all controls reachable and visible by keyboard |
| Videos without captions | Deaf or hard of hearing users | Add accurate captions and a transcript where possible |
| Unlabeled form fields | Screen reader users | Add proper labels and clear error messages |
| Links that say only "click here" | Screen reader users | Write link text that makes sense out of context |
| Text in images | Low vision users, screen reader users | Use real text |
| Pop-ups that trap focus | Keyboard and screen reader users | Ensure pop-ups can be closed and focus is managed |
| Fixed text sizes that do not scale | People who zoom | Use flexible layouts that work when zoomed |
How much does accessibility cost
Building accessibility into a new site adds some design and testing time, but it is typically a modest part of the total when planned from the beginning. Repairing a finished site depends on the platform and how many problems exist. An audit, which is an evaluation against WCAG, may be priced as a fixed fee or by size. Illustrative ranges might be a few hundred dollars for a simple automated scan and review, rising to several thousand dollars for a thorough manual audit of a larger site, and remediation is priced separately. Treat these as examples only and get quotes.
Worked example
A small online shop with 12 template types receives an audit finding 40 issues, most of them in the theme: missing alternative text, low contrast and unlabeled form fields. If a developer spends 12 hours at an illustrative $100 an hour to fix them, the cost is $1,200. The same fixes included in the original build might have added only a few hours. This is why asking about accessibility before hiring matters.
Why overlay widgets are not a complete solution
Some vendors sell "one-line" overlays that promise instant compliance. Accessibility professionals and many disability advocates have raised concerns that these tools cannot fix underlying code problems and may interfere with assistive technologies. The Federal Trade Commission has also taken action in at least one case concerning misleading claims about an accessibility product's ability to make sites compliant. Be skeptical of any product promising automatic, guaranteed compliance. Real accessibility comes from good design, correct code and testing with real tools and users.
What to ask a provider
- Do you build to WCAG 2.1 or 2.2 Level AA?
- How do you test: automated tools, manual keyboard testing, screen reader testing?
- Will you provide an accessibility statement or a summary of testing?
- How are third-party tools, such as booking widgets and chat, checked?
- What happens if an accessibility issue is found after launch, and is the fix included?
- Can you show an accessible site you have built?
Put the requirement in the contract. A line such as "The website will be designed and built to conform to WCAG 2.1 Level AA" gives you a way to hold a provider accountable. Note that automated tools find only a portion of the issues, so manual testing is important.
Practical steps you can take yourself
- Keyboard test. Put your mouse away and try to navigate your site using Tab, Shift+Tab, Enter and the arrow keys. Can you reach everything, and can you see where you are?
- Zoom test. Zoom your browser to 200 percent. Does the layout still work?
- Contrast check. Use a free contrast checker with your brand colors.
- Image review. Check that images have meaningful alternative text.
- Forms. Make sure every field has a visible label and errors are explained in text.
- Video. Add captions.
- Run a free automated scan, then fix what it finds, understanding it will not catch everything.
Building an accessibility habit
Accessibility is ongoing. New pages, new images and new tools can introduce problems. Assign someone to check new content, include accessibility in your maintenance plan and keep an accessibility statement with a way for users to report problems. Respond promptly to feedback.
Managing legal risk
If you receive a demand letter or complaint about website accessibility, do not ignore it and do not pay immediately. Keep the documents and speak with an attorney experienced in this area. Some demand letters are legitimate and some are mass-produced. A lawyer can help you evaluate your options. Proactively improving your site, documenting your efforts and having a way for users to contact you with problems are all sensible risk-reduction steps, though none provides a guarantee.
When to consult a professional
Talk to an attorney about your legal obligations, especially if you operate in a regulated sector, receive federal funds, sell to government or have received a complaint. Talk to an accessibility specialist for audits and remediation plans.
Frequently asked questions
Does my small business website have to be accessible?
It is a wise goal and may be a legal expectation, depending on your circumstances. The law is not uniform across the country, so ask an attorney about your situation.
Is WCAG a law?
WCAG is a technical standard, not a law, but it is widely used as a benchmark in settlements, agency rules and procurement.
Can a plugin make my site fully accessible?
No single plugin or overlay can reliably do that. It needs good design, clean code and testing.
Does accessibility hurt design?
Not when planned. Many accessible sites are visually polished, and the practices often improve usability for everyone.
Sources
- Web Accessibility Initiative (W3C) — WCAG and practical guidance.
- U.S. Department of Justice, Civil Rights Division — ADA information and web accessibility guidance.
- ADA.gov — official ADA information and resources.
- Centers for Disease Control and Prevention — disability statistics and public health information.
