How Accessibility Remediation Works
Remediation after an accessibility audit is a structured process that moves from the audit report through prioritization, code and content fixes, and verification. The audit identifies issues, documents their locations, and specifies which WCAG success criteria are not met. Remediation is the work of fixing those issues so the site moves toward WCAG conformance.
| Key Point | What It Means |
|---|---|
| Starting Point | The audit report, which lists every issue with its location, severity, and the WCAG criterion it violates |
| Prioritization | Issues are ranked by user impact and legal risk, not fixed in random order |
| Who Does the Work | Developers and content editors fix issues, sometimes with accessibility consultants providing guidance |
| Verification | Each fix is verified through screen reader testing, keyboard testing, and code inspection to confirm the issue is resolved |
What the Audit Report Contains
A professional audit report is the foundation for all remediation work. Each issue entry includes the specific WCAG success criterion that is not met, the location of the issue (page URL and element), a description of what is wrong, and recommended remediation steps.
This level of detail matters because developers need to know exactly where to look and what to change. A report that only lists issue types without locations adds hours of investigation before any fixing can begin.
How Issues Are Prioritized for Remediation After an Accessibility Audit
Not every issue carries the same weight. Prioritization typically uses two factors: user impact and risk.
User impact measures how much an issue affects someone’s ability to use the site. An image missing alternative text on a decorative background is low impact. A form that cannot be submitted using a keyboard is high impact because it blocks a core function entirely.
Risk considers the legal and reputational exposure an issue creates. Issues affecting primary user flows on public-facing pages carry more risk than issues on internal administrative screens. Organizations operating under ADA Title II requirements, which reference WCAG 2.1 AA, may weigh risk differently than those under Title III, where no specific technical standard is mandated but WCAG conformance is the widely accepted benchmark.
The Remediation Process
Once priorities are set, the work splits into two categories: code remediation and content remediation.
Code remediation involves developers modifying HTML, CSS, JavaScript, or ARIA attributes. This covers structural issues like missing form labels, incorrect heading hierarchies, and interactive elements that do not respond to keyboard input. Code remediation typically costs between 250 dollars and 550 dollars per page or screen.
Content remediation involves editors updating text alternatives, document formats, video captions, and other non-code assets. PDF remediation, for example, starts at approximately 7 dollars per page for document fixes.
Both tracks run in parallel when possible. A content editor can update image descriptions while a developer restructures navigation markup.
Verification After Fixes Are Applied
Fixing an issue is not the same as resolving it. Each remediation must be verified to confirm the issue no longer exists and that the fix did not introduce new issues.
Verification uses the same methods the original audit used: screen reader testing with NVDA, JAWS, or VoiceOver, keyboard testing across interactive elements, visual inspection at 200% and 400% browser zoom, and code inspection. Automated scans can supplement this process, but scans only flag approximately 25% of issues, so human verification is the primary check.
Tracking Progress
Organizations managing remediation across large sites benefit from tracking each issue through its lifecycle: identified, assigned, in progress, fixed, and verified. Compliance management platforms provide this tracking with dashboards and reporting. Smaller sites may use a spreadsheet mapped to the audit report.
The goal of tracking is visibility. Project teams, legal counsel, and project managers all need to see how much work remains and which high-priority issues are still open.
When Re-Evaluation Is Needed
After remediation is complete, a follow-up evaluation confirms the site’s conformance status. This is a second audit conducted against the same WCAG version and level as the original. The follow-up evaluation identifies any issues that were incompletely fixed or that emerged from new code deployed during the remediation period.
Ongoing monitoring through scheduled scans helps maintain conformance after the initial remediation cycle closes, catching regressions as the site continues to change.