Website accessibility remediation is the process of fixing accessibility issues identified during an evaluation. After an audit identifies where a website falls short of Web Content Accessibility Guidelines (WCAG) conformance, remediation is the work that brings it closer to meeting the standard.
| Key Point | What It Means |
|---|---|
| What Starts Remediation | An audit identifies specific issues against a WCAG conformance level, typically 2.1 AA or 2.2 AA |
| Who Does the Work | Developers, designers, and content authors, often guided by accessibility professionals |
| Typical Cost Range | Code remediation ranges from 250 dollars to 550 dollars per page or screen |
| Ongoing Nature | Remediation is not a one-time event; new content and features introduce new issues over time |
How Website Accessibility Remediation Works
Remediation begins with an audit report. That report lists each identified issue, its location on the site, the WCAG success criterion it violates, and guidance on how to fix it. Developers and content authors then work through the list, prioritizing by user impact and legal risk.
Some issues are code-level and require a developer. A missing form label, an improperly structured heading hierarchy, or a custom component that does not communicate its state to assistive technology all fall into this category. Other issues are content-level, such as images without adequate text alternatives or documents published in inaccessible formats.
The distinction matters because it determines who does the work and how long it takes.
Prioritization During Remediation
Not every issue carries the same weight. A screen reader user who cannot complete a checkout process faces a more significant obstacle than a user encountering a minor heading-level inconsistency on an informational page. Prioritization frameworks typically account for two factors: user impact and risk.
User impact measures how much the issue affects someone’s ability to use the site. Risk reflects the likelihood that the issue could lead to legal exposure under ADA Title III or another regulation. Issues scoring high on both factors move to the top of the remediation queue.
Code Remediation vs. Content Remediation
Code remediation addresses issues embedded in the site’s HTML, CSS, JavaScript, or ARIA implementation. This work typically requires front-end development resources and ranges from 250 dollars to 550 dollars per page or screen, depending on complexity.
Content remediation addresses issues within the material published on the site. PDF documents, images, videos, and editorial content all carry their own accessibility requirements. Document remediation, for example, starts at approximately 7 dollars per page for PDF files that need structural and tagging corrections.
The Role of Audits in Remediation
An audit conducted by an accessibility professional evaluates the site against a specific WCAG conformance level. The audit report becomes the remediation roadmap. Without it, teams are working from assumptions rather than documented findings.
Automated scans are part of the evaluation process, but scans only flag approximately 25% of issues. The remaining 75% require human evaluation through screen reader testing, keyboard testing, visual inspection, and code review. Remediation built only on scan results leaves the majority of issues unaddressed.
Remediation Is Not a One-Time Project
Websites change. New pages are published, features are added, third-party components are integrated, and content is updated. Each change can introduce new accessibility issues. Organizations that treat remediation as a single project often find themselves out of conformance within months.
Ongoing monitoring through scheduled scans identifies regressions in the areas automated tools can evaluate. Periodic audits identify issues across the full range of WCAG criteria. Together, they form the evaluation side of a continuous remediation cycle.
What Remediation Looks Like at the Organizational Level
Effective remediation programs assign clear ownership. Someone is responsible for tracking identified issues, coordinating fixes across teams, and verifying that completed work meets the conformance target. Accessibility compliance platforms support this by providing issue tracking, progress reporting, and prioritization tools.
Training also plays a role. When developers and content authors understand WCAG conformance requirements, they produce fewer issues in the first place. This reduces the volume of remediation needed after each audit cycle.
ADA Title II and Title III Considerations
Under ADA Title II, state and local government websites must conform to WCAG 2.1 AA. The rule went into effect with specific compliance deadlines based on entity size. Remediation for Title II entities is not optional; it is a regulatory requirement with a defined technical standard.
ADA Title III, which covers private businesses, does not specify a technical standard for websites. However, the Department of Justice has consistently referenced WCAG as the benchmark in settlements and guidance. Organizations reducing their Title III risk typically use WCAG 2.1 AA or 2.2 AA as their remediation target.
Measuring Remediation Progress
Progress is measured by the reduction in identified issues relative to the conformance target. After an initial audit, the total issue count serves as the baseline. Subsequent audits or re-evaluations after remediation cycles show how many issues remain.
Compliance platforms provide dashboards and reporting that track this over time, giving organizations visibility into their conformance trajectory rather than relying on periodic snapshots.
Remediation is where accessibility commitments become measurable. The audit identifies what needs to change, and remediation is the discipline of making those changes stick.