How to make a website ADA compliant
Making a website ADA compliant means bringing it to WCAG 2.1 AA, the standard courts and the Department of Justice reference, and being able to prove it. The work is a loop, not a project: audit, fix, verify, document, repeat on a schedule.
Here is the six-step process, in the order that reduces legal exposure fastest, with honest time and cost expectations for a typical small-business site.
Step 1-2: Scan everything, then prioritize by severity
Start with an automated WCAG scan of your key templates: homepage, product or service pages, and the full checkout or contact flow. Group findings by severity, not by page: one missing button label in your site header is one fix that clears every page at once. Critical and serious issues (unnamed controls, keyboard blockers, missing alt text) come first because they carry the most legal and usability weight.
Step 3-4: Fix at the source, then verify the fix
Fix issues in your actual theme, templates, and components: real alt attributes, real labels, real focus styles. Do not install an overlay widget; regulators have rejected them and the FTC has fined the marketing behind them. After each batch of fixes, re-scan to confirm the finding is gone and no new one appeared; regressions from template edits are common.
Step 5-6: Document everything and keep monitoring
Publish an accessibility statement describing your conformance status and a contact route. Keep dated records of every scan and every fix; that trail is what resolves demand letters cheaply. Then put scanning on a schedule: every deploy, plugin update, and content edit can reintroduce violations, and a site that was compliant last quarter can fail today without anyone touching code deliberately.
Compliance checklist
- Run a full-site WCAG 2.1 AA scan and export the findings
- Fix critical issues first: unnamed buttons/links, keyboard blockers, missing alt text
- Fix serious issues next: contrast failures, missing form labels, invisible focus
- Remove any accessibility overlay widget in favor of source-level fixes
- Re-scan after each fix batch to verify and catch regressions
- Add manual keyboard and screen-reader checks for your core flows
- Publish an accessibility statement with a contact method
- Schedule recurring scans and keep the dated evidence log
Frequently asked questions
- How long does it take to make a website ADA compliant?
- The handful of fixes that appear in most demand letters are usually done in days. Full WCAG 2.1 AA conformance on a small site typically takes 4-8 weeks of part-time work; large sites with custom components take longer. Monitoring then keeps it true.
- How much does ADA website compliance cost?
- Continuous automated scanning starts around $49/month. Full manual audits by specialist firms run $3,000-15,000 depending on site size. The expensive path is doing nothing: typical settlements run tens of thousands plus mandated remediation on a court's timeline.
- Can I just install a compliance widget?
- No. Overlay widgets do not confer compliance, the EU Commission and courts have said so, the FTC fined a leading vendor $1M over the claim, and plaintiffs' firms cite overlays in complaints. Fix the source.