Making a website ADA compliant requires a defined set of services that work together to bring content into WCAG conformance. The core services are a (manual) accessibility audit, remediation guidance, validation of fixes, and supporting documentation like an accessibility statement. User evaluation with people who rely on assistive technology adds another layer of confidence. Scans can supplement the work but cannot replace any of these services because scans only flag approximately 25% of issues. ADA compliance for a website is built through skilled human evaluation, targeted fixes, and confirmation that the issues identified have been resolved.
| Service | Purpose |
|---|---|
| Accessibility Audit | Identifies WCAG 2.1 AA issues across the website through expert manual evaluation |
| Remediation | Fixes the issues identified in the audit, either by your developers or an accessibility team |
| Validation | Confirms each fix resolves the original issue without creating new ones |
| User Evaluation | Real assistive technology users evaluate the experience for usability beyond code conformance |
| Documentation | Accessibility statement, policy, and audit report that demonstrate good-faith effort |
Why a Manual Accessibility Audit Comes First
The audit is the foundation. Without it, every other service operates on guesswork. A (manual) accessibility audit identifies the specific WCAG issues present on the site, where they appear, and what needs to change. Scans cannot do this work because they only flag approximately 25% of issues and cannot evaluate context, intent, or user experience.
The audit report becomes the document your developers work from during remediation. It also becomes evidence of a good-faith effort if your ADA compliance posture is ever questioned.
You can read more about how accessibility audits work and what the deliverable looks like.
Remediation: Fixing the Issues Identified
Remediation is where the audit report turns into action. Your development team works through the issues, prioritizing by user impact and risk. Most accessibility issues map to specific code changes: missing alt text, low color contrast, keyboard traps, unlabeled form fields, headings that skip levels.
Some teams complete remediation internally. Others bring in an accessibility consultant to either coach developers or perform the fixes directly. Either path works as long as the fixes are accurate and validated afterward.
Validation: Confirming Each Fix Resolves the Issue
Validation is the step that gets skipped most often, and it’s the one that confirms the work was done correctly. An auditor reviews each fix against the original issue. If a contrast ratio was supposed to move from 3.2:1 to 4.5:1, the auditor verifies the new ratio meets WCAG 2.1 AA. If a form field was missing a label, the auditor confirms the label is now associated programmatically.
Without validation, you don’t actually know whether your site moved closer to conformance or whether the fixes introduced new issues.
Does User Evaluation Belong in the Process?
User evaluation involves people who use screen readers, switch controls, voice recognition, or screen magnification working through your site. It catches issues code conformance alone cannot reveal: confusing flows, poorly worded labels, components that technically pass WCAG but are awkward to use with assistive technology.
For sites with transactions, account creation, or any task users must complete, user evaluation is the strongest evidence that real people can actually use the site. It also carries weight if you ever need to defend your accessibility posture.
Documentation That Supports ADA Compliance
Documentation rounds out the work. An accessibility statement explains the standard you conform to, the date of the most recent audit, and how users can report issues. An accessibility policy outlines your internal commitment and ongoing process. The audit report itself is the technical record of what was evaluated and what was identified.
Together these documents demonstrate that accessibility is part of how the organization operates, not a one-time project. This matters for ADA website compliance because courts and plaintiffs often look at intent and process, not just the current state of the site.
Ongoing Monitoring and Re-Audits
Websites change. New pages get published, themes update, third-party components get added. A site that was conformant six months ago may have new issues today. Ongoing monitoring through periodic scans helps catch regressions quickly, and a re-audit on a defined cadence keeps your ADA compliance posture current.
Accessible.org clients often pair monitoring with annual audits depending on how frequently the site changes. For sites under active development, more frequent evaluation makes sense.
FAQ
How much do the services needed to make a website ADA compliant cost?
Cost depends on the size and complexity of the site. A small informational website may need a smaller audit and limited remediation. A large ecommerce site or web app requires more pages evaluated, more developer time, and validation across more templates. The audit is typically the first investment, and remediation costs follow from what the audit identifies.
Can a scan alone make a website ADA compliant?
No. Scans flag approximately 25% of issues and cannot evaluate context, alternative text quality, keyboard flow, or whether interactive components work with assistive technology. A site that passes every automated scan can still have serious WCAG issues. The (manual) accessibility audit is the only way to determine WCAG conformance.
Do I need user evaluation if I already have an audit?
User evaluation is not required for WCAG conformance, but it adds a layer of evidence that real users can use the site. For high-traffic or transaction-heavy websites, user evaluation strengthens both the user experience and the legal posture.
How long does the full process take?
An audit typically takes a few weeks depending on scope. Remediation timing depends on your development team’s capacity and the volume of issues identified. Validation follows remediation and is usually faster. Most websites can move through the full cycle in a few months.
Contact Accessible.org to scope the services needed for your website. Contact our team to get started.
