How to Make a Small Business Website ADA Compliant Without Spending a Fortune

A prioritized, phased guide for small business owners who want real ADA website compliance — not an overlay subscription — without blowing their budget.

You Do Not Need a $50,000 Enterprise Audit

Enterprise accessibility audits are scoped for large applications with hundreds of templates, authenticated workflows, and complex interactive components. A typical small business site — a homepage, a few service pages, a contact form, maybe a blog — has a much smaller surface area. The defects that generate demand letters tend to cluster around the same handful of issues: missing image descriptions, unlabeled form fields, poor color contrast, and interactive elements that cannot be reached with a keyboard. Fixing those issues systematically, documenting the work, and maintaining the fixes over time is what "good-faith compliance" actually means in practice.

Phase 1: Quick Wins Any Owner Can Do

These tasks require no coding knowledge. They address the most commonly cited WCAG 2.1 and 2.2 Level AA failures on simple sites.

Add Alt Text to Images (Estimated time: 1–3 hours for a 50-page site)

Every image that conveys information needs a short, accurate text alternative in the alt attribute. Purely decorative images should carry an empty alt="" so screen readers skip them. Most website platforms — WordPress, Squarespace, Wix, Shopify — expose an "alt text" field in the media library. Work through your images page by page and fill in descriptions that serve a user who cannot see the image. WCAG Success Criterion 1.1.1 (Non-text Content) is the specific requirement.

Fix Form Labels (Estimated time: 30–90 minutes)

Every input field — name, email, phone, search — must have a visible label that is programmatically associated with that field. If your contact form uses placeholder text instead of a real label, it will fail. In most platforms you can enable labels through form settings without touching code. WCAG SC 1.3.1 and 4.1.2 both address this.

Verify Keyboard Navigation (Estimated time: 30–60 minutes)

Press Tab to move through your site without a mouse. Every link, button, and form control should receive a visible focus indicator and should be reachable in a logical order. If focus disappears or jumps unpredictably, note where. Some of those issues can be resolved by removing outline: none from your theme's CSS — others will surface as Phase 2 work. WCAG SC 2.1.1 and 2.4.7 govern this area.

Check Your Page Titles and Heading Structure (Estimated time: 30–60 minutes)

Each page should have a unique, descriptive <title> element and a single <h1> that describes the page's purpose. Subheadings should nest logically (h2 before h3). Most platforms let you edit the page title in SEO settings and heading tags in the page editor.

Phase 2: What Requires a Professional

The following issues cannot be resolved through a platform's admin interface. They require changes to theme code, custom components, or JavaScript behavior.

ARIA Landmark Structure

Screen reader users navigate pages by jumping between landmarks: header, nav, main, footer. If your theme's HTML doesn't include these semantic elements or correct ARIA roles, a developer needs to add them to the theme templates directly.

Color Contrast in CSS

WCAG SC 1.4.3 requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. If your brand palette doesn't meet those thresholds, a developer adjusts the color values in the stylesheet. This cannot be reliably patched by a JavaScript overlay because the overlay would need to recolor text on every page load without causing visual artifacts — a known failure mode of that approach.

Focus Management in JavaScript Components

Modals, dropdown menus, accordions, and carousels built with JavaScript require explicit focus management: when a modal opens, focus must move into it; when it closes, focus must return to the triggering element. This is WCAG SC 2.4.3 (Focus Order) and 4.1.2 territory, and it requires code changes inside the component itself.

Why Overlays Do Not Solve Phase 2 Problems

Accessibility overlays are JavaScript widgets that load after your page renders and attempt to modify the DOM or intercept user interactions. They cannot reliably fix reading order, semantic structure, or complex widget behavior because those problems exist in the underlying markup, not at the surface layer the script can reach. Users who rely on their own screen reader or assistive technology settings often find that overlay scripts conflict with their tools, adding a barrier rather than removing one.

Courts have generally not accepted the presence of an overlay as an ADA defense; lawsuits have continued — and in some cases named the overlay itself as a barrier. In 2025 the FTC reached a settlement with accessiBe, one of the largest overlay vendors, including a $1,000,000 penalty, over how its automated-compliance claims were marketed to businesses. WCAGDefender's scanner specifically detects when a site has an overlay installed, because that presence is a known risk factor in demand letters rather than a mitigating one.

Cost Comparison: Three Paths for a Small Business

Where WCAGDefender Fits for Small Business Owners

WCAGDefender is a veteran-owned small business built specifically for sites that don't have an in-house developer or a five-figure audit budget. The free instant scan at wcagdefender.com runs against WCAG 2.1 and 2.2 Level AA and returns a lawsuit-risk read — not a vague grade — on any public URL, with no account required. If the scan surfaces issues that need real-code fixes, the paid service delivers platform-specific remediation steps for WordPress, Shopify, Wix, and Squarespace, with every fix reviewed for accuracy before delivery. The documentation package — accessibility statement, remediation record, VPAT, IRS credit worksheet, and a draft demand-letter response — is designed to demonstrate good-faith effort if a complaint is ever filed.

Frequently asked questions

Is WCAG 2.2 required by law for small businesses?

There is no federal regulation that explicitly cites WCAG 2.2 as the required standard for private business websites under ADA Title III. However, the DOJ and federal courts treat WCAG 2.1 Level AA as the practical benchmark for determining whether a website is accessible under the ADA. The DOJ's 2024 Title II rule formally adopts WCAG 2.1 AA for state and local government sites. For private businesses, meeting WCAG 2.1 or 2.2 Level AA is the accepted yardstick used in litigation and demand letters, so treating it as the target is the prudent approach.

What is the cheapest compliant option for a small business website?

The lowest-dollar starting point is doing Phase 1 fixes yourself — alt text, form labels, heading structure, page titles — which costs only your time. Those fixes address common demand-letter triggers and demonstrate good faith. Phase 2 structural issues (ARIA landmarks, color contrast in CSS, JavaScript focus management) require developer work and represent the realistic minimum for a site with any interactive components. A managed real-code remediation service with fixed-scope pricing is typically more cost-effective over time than a monthly overlay subscription, especially when you factor in the overlay's ongoing fees and its documented legal risks.

How do I prove my site is accessible if I receive a demand letter or get sued?

Documentation is what demonstrates good-faith effort to a court or opposing counsel. Useful records include: a dated accessibility statement on your site, a log of specific defects identified and remediated with dates, a VPAT (Voluntary Product Accessibility Template) covering your site's features, and ideally a professional remediation report. WCAGDefender produces all of those, plus a draft demand-letter response, as part of its paid service. An overlay vendor's marketing materials do not constitute a remediation record and have not been accepted as a legal defense.

Do accessibility overlays like accessiBe or UserWay protect me from ADA lawsuits?

The documented record says no. Courts have generally not accepted overlay installations as a defense in ADA website cases, and some plaintiffs have named the overlay itself as a barrier. In 2025 the FTC settled with accessiBe over how its automated-compliance marketing was presented to businesses, with a $1,000,000 penalty. Overlays sit on top of existing markup at page load; they cannot reliably fix structural problems like reading order, semantic landmarks, or complex interactive widgets — and they can conflict with users' own screen reader settings.

How long does it take to make a site under 50 pages accessible?

Phase 1 work — alt text, form labels, heading structure, page titles, basic keyboard checks — typically takes a non-developer four to six hours spread across one or two sessions for a site of that size. Phase 2 work depends on how complex the theme and any custom components are; a simple informational site may need only a few hours of developer time, while a site with custom JavaScript widgets or a complex checkout flow will take longer. A free scan from WCAGDefender can identify exactly which issues are present before you scope the work.

Does Section 508 apply to my small business website?

Section 508 applies to U.S. federal agencies and organizations that receive federal funding or sell products and services to the federal government. It does not apply to most private small businesses selling to general consumers. The relevant law for private business websites is ADA Title III. If your business has any contracts with federal agencies, Section 508 compliance — which aligns to WCAG 2.0 Level AA — may be required for those contracts specifically.