Making a website ADA compliant means bringing it into conformance with WCAG 2.1 AA, the standard courts and federal agencies treat as the practical benchmark for the Americans with Disabilities Act. The path has three core stages: a manual accessibility audit identifies the issues, remediation addresses them, and validation confirms the fixes hold. Automated scans flag approximately 25% of issues, so a fully manual audit is the only way to know what conformance looks like on your site. Once the work is complete, an accessibility statement documents the result. That is the full picture, condensed.
| Stage | What Happens |
|---|---|
| Standard | WCAG 2.1 AA is the working benchmark for ADA website compliance. |
| Audit | A fully manual audit identifies every WCAG 2.1 AA issue on representative pages. |
| Remediation | Developers fix issues based on the audit report, prioritized by user impact and legal risk. |
| Validation | The auditor reviews fixes and confirms conformance. |
| Documentation | An accessibility statement records the standard met and the date of conformance. |
What ADA Compliance Means for a Website
The ADA does not name a technical standard for websites. In practice, courts, the DOJ, and the accessibility industry treat WCAG 2.1 AA as the working standard. If your site conforms to WCAG 2.1 AA, you have a strong, defensible position under Title III for private businesses and Title II for state and local government entities.
WCAG 2.2 AA is also accepted and increasingly requested, particularly for newer projects. Either version is appropriate for ADA compliance work.
Start With a Manual Accessibility Audit
The first real step is a fully manual accessibility audit performed against WCAG 2.1 AA. An auditor reviews a representative sample of pages and templates, evaluates each WCAG criterion, and produces a report that identifies every issue with location, severity, and recommended fix.
Automated scans have a role, but they only flag approximately 25% of issues. They cannot determine conformance. The remaining issues, which include keyboard traps, focus order problems, semantic structure errors, and most ARIA misuses, require a human evaluator.
Accessible.org audits are always 100% manual. The output is a report your development team can act on without guesswork.
How Long Does It Take to Make a Website ADA Compliant?
Timeline depends on site size, complexity, and how quickly the development team can complete remediation work. A small informational site can move from audit to validation in a few weeks. A larger ecommerce site or web app can take two to three months when remediation runs in parallel with normal release cycles.
The audit itself typically takes one to three weeks. Remediation is the variable. Validation, once fixes are in place, is faster than the original audit because the auditor is reviewing specific items rather than evaluating the full standard from scratch.
Remediation: Fixing the Issues
Remediation is where developers address each issue in the audit report. Prioritization matters. The most useful approach is to group issues by severity and template, then work through them in order of user impact and legal exposure.
Common remediation work covers code-level fixes such as missing or inaccurate alt text on meaningful images, form fields without programmatic labels, low color contrast on text and interactive elements, keyboard inaccessibility on custom components, missing or incorrect heading structure, and ARIA roles applied where native HTML would serve better.
Many of these fixes are simple once a developer has the report and understands the WCAG criterion behind each item. Some, particularly those involving custom widgets or dynamic content, require more careful work.
Validation Confirms Conformance
After remediation, the auditor reviews the fixes. Validation is not a second audit. It is a targeted review of every issue from the original report, confirming each one has been addressed correctly.
If something was not fixed properly, it goes back to the developer with notes. Once the validation pass is clean, the site can claim WCAG 2.1 AA conformance with documentation to back it.
Documenting the Work
An accessibility statement on the site documents the standard met, the date of conformance, and how users can report issues. This statement is not legally required, but it signals good faith and gives users a contact point.
For ongoing maintenance, plan to re-audit when significant changes ship. New templates, redesigns, and major feature releases reintroduce risk. A short re-audit on changed areas keeps the site in conformance over time.
What About Scans and Monitoring?
Scans are useful for catching regressions between audits. They are not a substitute for the audit itself. A scan can tell you that an image is missing alt text. It cannot tell you whether the alt text on another image is accurate or meaningful.
Use scans to monitor. Use audits to determine conformance. The two activities support each other but answer different questions.
FAQ
How much does it cost to make a website ADA compliant?
Cost depends on site size and complexity. A small informational site audit can run a few thousand dollars. Larger sites and web apps cost more because there are more templates, components, and user flows to evaluate. Remediation cost depends on how many issues the audit identifies and whether your team or an outside developer performs the work.
Is WCAG 2.1 AA legally required for ADA compliance?
The ADA itself does not name WCAG. Title II of the ADA, as updated by the DOJ rule for state and local governments, does require WCAG 2.1 AA. For Title III (private businesses), WCAG 2.1 AA is the de facto standard courts apply when evaluating accessibility claims.
Can AI or automated tools make a website ADA compliant?
No. AI can support parts of the workflow, like helping a developer interpret an audit issue or draft a fix faster. Accessible.org Labs is actively researching how AI can make auditing and remediation work more efficient. But AI cannot evaluate WCAG conformance on its own, and no automated tool can make a site ADA compliant without human review.
How often should I re-audit my website?
A full re-audit is appropriate after major redesigns or feature launches. For sites under active development, a yearly re-audit on key templates keeps things current. Between audits, scans and internal review can catch obvious regressions.
Closing Thought
ADA website compliance is not a one-time project that ends with a certificate. It is a standard you meet, document, and maintain as the site evolves. The work is concrete, the path is known, and the outcome is a site that more people can actually use.
Contact Accessible.org to start an audit and map the path to ADA compliance for your site. Contact Accessible.org.
